Docker Compose with one Terminating Container

Question

I'm having a docker compose setup of a database container, an application container and one container which pre-loads the database with necessary data.

I want to start all of the containers together with docker-compose up while the pre-loading container terminates after it has completed it work with exit 0.

But terminating this one container takes down the complete setup with the message:

composesetup_load_1 exited with code 0
Gracefully stopping... (press Ctrl+C again to force)
Stopping composesetup_app_1...
Stopping composesetup_db_1...

Is there any way of having multiple containers with different life-time in one docker-compose setup? If yes, how?

score 8 · Accepted Answer · answered Jun 23 '15 at 11:08

8

My workaround for now is to keep the pre-loading container running by adding tail -f /dev/null to the end of the entrypoint script. This keeps the process running, while nothing actual happens.

answered Jun 23 '15 at 11:08

white_gecko

4,808
4
55
76

Is this a common method of doing this sort of thing? Is there a "right" / "official" way to do this? I love this slick solution, in either case. – IcyFlame Feb 02 '18 at 19:17
This, so much. Thanks – Pricey Dec 19 '18 at 03:03
1

Clever, but it'd be better to `sleep inf` – inetknght Apr 24 '19 at 15:52

score -1 · Answer 2 · answered Jul 31 '17 at 16:03

-1

Using -d option at docker-compose up -d will run the process in detached mode. This avoids the need to kill the service with Ctrl+C and therefore stop the containers.

Note: I am asumming you killed the process with Ctrl+C from the message "Gracefully stopping... (press Ctrl+C again to force)" you shared.

answered Jul 31 '17 at 16:03

atfornes

468
5
21

1

No, I've not terminated the process with Ctrl+C the process has just completed its work and thus terminates with `exit 0`. So running docker-compose with the `-d` option is no solution. – white_gecko Aug 01 '17 at 09:36
1

@white_gecko, ok, thanks for clarifying. The behaviour is then as if the flag `--abort-on-container-exit` was set? – atfornes Aug 01 '17 at 16:05
1

Ok, maybe this flag is a solution … when I've posted the question at least this behavior was default. – white_gecko Aug 02 '17 at 07:47

Docker Compose with one Terminating Container

2 Answers2