January-10th-2020, 07:57 AM
(This post was last modified: January-12th-2020, 06:18 PM by Armin@netPI.)
Since you have two commands that need to be started a single ENTRYPOINT reference will not help you.
Look to our ENTRYPOINT tag ... it points to "/etc/init.d/entrypoint.sh" ... if you now analyze this file you see it starting all the needed final scripts one after the other. This is how you have to do it as well.
Even if you commit a running container ... the entrypoint will remain. So if you do not want to write your own Dockerfile and container and want to stay with the committing procedure ... then make your edits in the running container in the "/etc/init.d/entrypoint.sh" file meeting your needs and make then a commit after exiting the container.
A commit will store only what's "inside" the container. If the mariadb data is in the container then it will be committed as well. External mapped volumes aren't.
In general: what else you can do with volumes you can read here https://docs.docker.com/storage/volumes/
Thx
Armin
Look to our ENTRYPOINT tag ... it points to "/etc/init.d/entrypoint.sh" ... if you now analyze this file you see it starting all the needed final scripts one after the other. This is how you have to do it as well.
Even if you commit a running container ... the entrypoint will remain. So if you do not want to write your own Dockerfile and container and want to stay with the committing procedure ... then make your edits in the running container in the "/etc/init.d/entrypoint.sh" file meeting your needs and make then a commit after exiting the container.
A commit will store only what's "inside" the container. If the mariadb data is in the container then it will be committed as well. External mapped volumes aren't.
In general: what else you can do with volumes you can read here https://docs.docker.com/storage/volumes/
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
