-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker #12
Comments
I had Labrador running in Docker as I wanted to run multiple versions on a single server. However, I ran into issues with email notifications. I'd be interested in getting the Docker version working properly so +1 for this suggestion. I have 5 none-Docker Labrador sites running at the moment, with plans for ~5 more. It takes less than 5 mins to deploy each one. |
Hi both, Thanks for the suggestion @jcgrenier - I can certainly see the advantage of running Labrador in a nice clean Docker environment, and it would be a lot easier to set up if there was a public image to pull for sure. I've used Docker a tiny bit (though I've never run a website from a docker image), but I don't see why it shouldn't be possible to release such an image. @darogan - do you have a blank image floating around already? Would save me making one.. As for e-mail, well, e-mail is hard.. 😄 It's the single Labrador issue that we ran into again and again at Babraham, mostly due to firewalls. But it should be possible to get some kind of mail service running inside docker which can then send mail (a quick google reveals a lot of people asking similar questions). Whether they make it through the institute mailserver is a different matter though. Phil |
Yeah, I think this could be a good addition!! Thanks for letting me know when it becomes available! JC |
@ewels I had a quick look for my images. One was setting up a docker web server and the other containing Labrador. I don't think they will be particularly useful in their current state, but I can create a new one over the next week if that helps? |
If you don't mind then that would be great - I don't use labrador myself any more, or docker really. If it's a lot of work for you then I don't mind looking into it (it would be good for me to get more practice doing this stuff), but if you have a recipe kicking around which would be easy to generalise then that would certainly help.. Phil |
4 years later and @StevenWingett has written some documentation based on my emailed recommendations. Again sending email is an issue. Could be good to think about a custom image still I think. Should be easy enough to set up (apart from the email bit). |
Hi Phil!
Thanks again for this incredible tool!
The following is more a suggestion than an issue in itself.
Have you ever think about creating a public Docker for this? On many systems where we could think of using it for our own data for example, we don't want to play with system related configuration. A docker could be a great way to easily install the tool on a server and by the same time taking all the httpd, apache2, etc. installation.
I will probably start very soon to work on that, but I don't know a lot about Dockers so far, need to do some testing before implementing it.
Best,
JC
The text was updated successfully, but these errors were encountered: