return from docker-compose up in jenkins

Question

I have base image with Jboss copied on it. Jboss is started with a script and takes around 2 minutes.
In my Dockerfile I have created a command.

CMD start_deploy.sh && tail -F server.log

I do a tail to keep the container alive otherwise "docker-compose up" exits when script finishes and container stops.

The problem is when I do "docker-compose up" through Jenkins the build doesn't finishes because of tail and I couldn't start the next build.

If I do "docker-compose up -d" then next build starts too early and starts executing tests against the container which hasn't started yet.

Is there a way to return from docker-compose up when server has started completely.

score 0 · Answer 1 · answered Jun 06 '16 at 23:51

0

Whenever you have chained commands or piped commands (|), it is easier to:

easier wrap them in a script, and use that script in your CMD directive:
```
CMD myscript
```

or wrap them in an sh -c command:

sh -c 'start_deploy.sh && tail -F server.log'

(but that last one depends on the ENTRYPOINT of the image.
A default ENTRYPOINT should allow this CMD to work)

answered Jun 06 '16 at 23:51

VonC

Do you mean that if I wrap them in separate script & use that script in CMD, I would be able to return from docker-compose up when both scripts are executed ? – Manish Kumar Thakur Jun 08 '16 at 04:37
@ManishKumarThakur yes, that is the idea. – VonC Jun 08 '16 at 06:35
I'll try that. Would let you know. Thanks. – Manish Kumar Thakur Jun 08 '16 at 09:05
That didn't help. Result is same. I created a script startConatiner.sh & put the two commands in there. docker-compose starts the tailing and didn't return. – Manish Kumar Thakur Jun 10 '16 at 12:00
@ManishKumarThakur would it return without the tailing? – VonC Jun 10 '16 at 12:28
Without tailing it would return & container will exit. – Manish Kumar Thakur Jun 10 '16 at 12:30
@ManishKumarThakur So isn't it expected for the command to *not* return then? (since, if it was returning, the container would exit) – VonC Jun 10 '16 at 12:31
I want it to return but container should somehow run in background. – Manish Kumar Thakur Jun 10 '16 at 12:47
@ManishKumarThakur Then can you try and use a supervisord? (http://stackoverflow.com/a/19273735/6309): it will prevent the container to exit early and monitor your processes – VonC Jun 10 '16 at 12:54
@ManishKumarThakur Or, simpler, run it in daemon: docker run -d. But in your case (docker-compose -d) that didn't work. So I would still use a supervisord. – VonC Jun 10 '16 at 12:55

1 Answers1