Provide Docker file to create a dev environment

[scolapasta]

Step 1: install basic services: postgrsql, solr, glassfish, etc.
Step 2: Run equivalent of installer script
Step 3: ???
Step 4: Profit!

[scolapasta]

Step 0: Investigate what community has already done in this direction.

[stevenmce]

It may be worthwhile looking at this for a production environment as well. We are considering this for ADA. Cheers Steve (@stevenmce)

…

Sent from my iPhone On 21 Jun 2017, at 5:53 am, Gustavo Durand <notifications@github.com<mailto:notifications@github.com>> wrote: Step 0: Investigate what community has already done in this direction. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#3938 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABKtU6yCcF6NMr86BCDwWwGyrN8663Lhks5sGCMrgaJpZM4OAEtS>.

[pdurbin]

The most recent work on Dockerizing Dataverse was done by @joelmarkanderson and @telnoratti in https://github.com/IQSS/dataverse-aws but I haven't heard from them in a bit. Hopefully they'll see this comment and let us know if they'd be willing to help us get up to speed with Dataverse on Docker and let us know the state of that repo.

I also tested bjonnh@f7a82c9 by @bjonnh a while back and it worked fine. This was an attempt to add a Dockerfile and related files directly to the main Dataverse repo. The goal was to have a place to run integration tests (API tests using REST Assured) on pull requests as they come in.

Finally, we can take a look at https://github.com/nds-org/ndslabs-dataverse/blob/master/dockerfiles/dataverse/Dockerfile by @craig-willis

If there are other Dataverse on Docker efforts out there, they aren't top of mind for me. Sorry if I'm forgetting anyone.

[pdurbin]

Yesterday @bjonnh and I chatted about how much work with thing this issue entails. Our guess is a full-time week for someone who already knows Docker:

bjonnh: pdurbin: saw your ping on github
pdurbin ah, this ping: #3938 (comment)
pdurbin bjonnh: I was wondering about docker build -t bjo/dataverse ... I assume we don't want "bjo" in there since it's you. :)
bjonnh: I still have some work to do on it
bjonnh: I see no problem giving it to something like dataverse/dataverse
bjonnh: well
bjonnh: I would like a docker compose that spins up multiple containers linked together
bjonnh: se we can separate solr and everything properly
bjonnh: that would help isolating issues
pdurbin bjonnh: ok. I think we might be attempting to estimate #3938 as soon as this afternoon. Do you have any idea how much work this would be?
bjonnh: in term of what?
bjonnh: I think it could be achieved in a full-time week (which I wish I would have), but don't quote me on that
bjonnh: pdurbin: ^
pdurbin bjonnh: ok, so a week for someone who actually knows Docker. Thanks!
bjonnh: yep

In other news, over at #3927 I'm asking developers who use Windows if they'd be interested in running Dataverse within Docker on their dev machines. In the context of a Windows dev environment, only one opinion on Docker has been given so far, which is "it could be a little difficult and it seems not necessary now."

[craig-willis]

We'd welcome an official set of Dataverse images for use in our system. Note that we also have separate Dockerfiles for Rserve, Solr, and TwoRavens. These are all implemented to fit into the NDS Labs Workbench, but could also work with docker compose.

https://github.com/nds-org/ndslabs-dataverse/tree/master/dockerfiles

It's worth noting that I hacked the Dataverse install process a fair amount to try to separate out the installation process, which could go into "docker build" from the configuration process needed during "docker run". This hasn't been revisited in 9+ months.

[pameyer]

@craig-willis I'm glad you saw this; the work that NDS Labs Workbench did on dockerizing Dataverse (and it's dependencies/components) has come up in some of these discussions.

There's been a little bit of work done with the Dataverse installer (more for non-interactive use than splitting components), but this installer might be getting reworked (#3937) : so any suggestions / comments about areas that could go smoother for this type of installation would be helpful.

[pameyer]

One thing that didn't occur to me to mention during initial discussions is that there may be a conflict between file storage (glassfish file storage directory), shared/persistent storage in docker, and running glassfish as root. May turn out not to be an issue, but something to check.