Run a database migration command when deploying a Docker container to AWS

Question

Please bear with me. Pretty new to Docker.

I'm deploying Docker containers (detached) to an AWS EC2 registry using CodeDeploy. On deploy, the following command is run after setting some environmental variables etc:

exec docker run -d ${PORTS} -v cache-${CACHE_VOLUME} --env-file $(dirname $0)/docker.env --tty "${IMAGE}:${TAG}"

The container runs an image located and tagged in EC2 Container Service. No problems so far.

Since this is a PHP application (specifically a Symfony2 application) I would normally need to issue the following command to execute database migrations on deployment:

 php app/console doctrine:migrations:migrate --no-interaction

Now, is there any to run this command during "docker run..." while keeping the container running, or do I need to run another container specifically for this command?

Many thanks!

migu · Accepted Answer · 2023-03-01 17:23:22Z

18

You need to create an entrypoint. This script runs at the container startup.

entrypoint.sh file:

# create or update db
./wait-for-it.sh <DB_HOST>:<DB_PORT> -t 30
php app/console doctrine:migrations:execute 

# start apache
apache2-foreground

wait-for-it is a script that waits until the database is started.

edited Mar 1, 2023 at 17:23

migu

1,4011 gold badge15 silver badges23 bronze badges

answered Jan 11, 2017 at 13:34

Bukharov Sergey

10.3k5 gold badges43 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Alex Regenbogen · Accepted Answer · 2017-03-10 10:43:52Z

8

Just leaving this here for the next one that searches for this... ;-)

When using a recent version of Doctrine, there is a pretty handy parameter for this:

php bin/console doctrine:migrations:migrate --no-interaction --allow-no-migration

The "allow-no-migration" parameter instructs doctrine not to throw an exception, when there is nothing to do...

answered Mar 10, 2017 at 10:43

Alex Regenbogen

6085 silver badges5 bronze badges

Comments

enno.void · Accepted Answer · 2017-01-26 18:51:32Z

1

I do as follows:

docker-compose exec [containerID] ./app/console migrations:migrate --no-interaction

edited Jan 26, 2017 at 18:51

answered Jan 11, 2017 at 13:51

enno.void

6,6284 gold badges28 silver badges45 bronze badges

4 Comments

Fredrik Over a year ago

But how can the deployment script know the [containerId]? Or are you running it manually?

enno.void Over a year ago

I do it manually. But i think u could do a "docker ps" in your deployment-script and grep the containerId you would apply to...

eawenden Over a year ago

This mixes two possible solutions. docker-compose run [service] would spin up a new docker container. You can also use docker ps to find out the container id of the running php container and use docker exec [containerID] [migrationCommand] to run the command inside the running container instead of spinning up a new one.

yuklia Over a year ago

@mr.void but you can't do using Swarm mode

Collectives™ on Stack Overflow

Run a database migration command when deploying a Docker container to AWS

3 Answers 3

Comments

Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related