Save Logs During Container Startup about docker-maven-plugin HOT 4 CLOSED

Logs should be printed during start-up, regardless of whether the container fails or not. If that is not the case, then this is a bug.

from docker-maven-plugin.

I guess the general request here was to put the logs additionally to the save-logs path, in order to have a single point to look at in case of an issue.

from docker-maven-plugin.

@marcust Yes, that is correct. The desired functionality would help when running CI builds. When a build is run on Jenkins, the full output from each of the containers is written to the save-logs path. In the event that one of the containers fails to start up, the save-logs path contains the output from all of the containers that started successfully and the one that didn't.

I think that the current behavior requires looking at the console output to debug container startup issues, which sometimes lacks information because it stops displaying log output for container A once container A has started. When container B starts, the output of container A stops being displayed, but the reason for the failure of container B's startup might be found by reviewing container A's log output. In this case, we usually go look at the logs directly through Docker, but this approach is more difficult when debugging CI builds.

from docker-maven-plugin.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-maven-plugin.