You cannot start the docker build process with an variable (eg. a var that holds a specific branch to checkout) in your dockerfiles.
2. Managing the build process,starting and linking of multiple images/containers
I started with bash scripts then switched a tool called fig. Even though fig keeps things in a simple config file for whole setups I cannot use it because it does not wait for the DB container until it's ready to accept connections before starting a container that links to it.
So I'm back writing bash scripts.
3. Replacing running containers
Restarted containers get a new IP, so all the linking does not work anymore. I had to setup a DNS server and wrap the restarting of containers in bash scripts again.
I had no big issues creating a private registry after the ssl certificate was created correctly.
1. Dockerfiles are to static
You cannot start the docker build process with an variable (eg. a var that holds a specific branch to checkout) in your dockerfiles.
2. Managing the build process,starting and linking of multiple images/containers
I started with bash scripts then switched a tool called fig. Even though fig keeps things in a simple config file for whole setups I cannot use it because it does not wait for the DB container until it's ready to accept connections before starting a container that links to it. So I'm back writing bash scripts.
3. Replacing running containers
Restarted containers get a new IP, so all the linking does not work anymore. I had to setup a DNS server and wrap the restarting of containers in bash scripts again.
I had no big issues creating a private registry after the ssl certificate was created correctly.