-
Notifications
You must be signed in to change notification settings - Fork 37
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
Use compose #7
Comments
I don't know anything about compose. It sounds cool though. |
I'm not convinced that I should use compose here (although to be honest, I still don't really know what it is).
That sounds pretty good. I can't imagine it would be any easier than using volumes though.
It takes about 2.3 seconds to spawn the container on my system. Since this is a once per week type task, I'm not too interested in this benefit.
This can be done now. There's nothing in this image that hard codes the ownCloud server to use the MySQL server provided here, the user can point OC to whatever database they like during initial setup. I'm sure there are a plenty of MySQL server images one could pull from the Docker Registry that would work just fine here. I just decided to build a MySQL server in for convenience. Also, I'm not so sure that that OC and mariadb would impact each other any less if they were running in different containers, unless you're using settings that cap the container's resource usage. |
docker compose would allow you to write a small definition that defines an organization of docker containers, i.e. one could have one owncloud container with the standard ports exposed readily linked to a mysql container and having a volume container for all data stuff. Thats just one command for the user to get the default configuration then which is nice IMO. |
Please see https://github.com/tkock/owncloud-docker-compose for my setup with docker-compose using your Dockerfile. |
Related: owncloud-archive/documentation#1516 and #41 |
I think it would be nice to use compose to create a net of docker images for an owncloud distribution:
The text was updated successfully, but these errors were encountered: