Data container is not running

[dzentota]

By convention: all containers SHOULD keep running, eg. data-containers with tail -f /dev/null

Does it mean that in docker-compose.yml command /bin/bash should be replaced with tail -f /dev/null ?

[schmunk42]

Isn't this this still under discussion?

We had the setting you mentioned and ran into problems with logspout containers.
We got an error about Too many open files, since the data only container opened so many pointers - I guess.
At least that was our explanation and the error was gone after letting the container exit with status 0.

Do you use a tool which requires all containers in a stack to be running?

[schmunk42]

By the way ... we're working on a setup without any data containers at all ;)

[philippfrenzel]

so how about a datacontainer for elastic search e.g. because that could be integrated "easy" ;)

[Quexer69]

ATM, just fire tail -f /dev/null for this container...?

Your decision if you need to keep them up and running :)

[dzentota]

just confused with https://github.com/phundament/app/blob/master/docs/advanced/61-coding-conventions.md

also in stacks-gen/*.yml command: 'tail -f /dev/null' but in docker-compose.yml command: '/bin/bash'

[schmunk42]

We still need to update the docs, but I just wanted to let you know that we've removed the data-container and have a much simpler setup now, see https://github.com/phundament/app/blob/master/docker-compose.yml