-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Running container in foreground #54
Comments
@hron84 |
I currently have a Git repository with Nagios configuration files and I use docker-compose to create a Nagios container with same version as the production and check the configuration files (I don't want to actually run a Nagios server, since it's not neccessary and could not work because a whole different networking conditions. I just want to check configuration files from syntax, and dependency aspect). The docker-compose.yml:
After starting the tests, Nagios runs a few checks and exits. If the Nagios encounter any problems it logs to the standard output/standard error streams. But since I cannot see immediately the output of the output of the container, I lose the information about why the tests are failed. Running I know there is a workaround for this problem but since docker-compose itself already supports running multiple containers in the foreground I just can't see why PoCo cannot do the same. |
Ah, I see. But you know, the docker holds the log after the container exited too. When you have an exited (or running) container, you can get the previous logs by So, you can use this command to check your nagios configuration: |
Currently,
poco up plan
always start containers behind the scenes. In some cases it would be more useful, if the container could be started in foreground, like how thedocker-compose up
works.The text was updated successfully, but these errors were encountered: