We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to expose the t parameter of the stop call (see https://docs.docker.com/reference/api/docker_remote_api_v1.20/#stop-a-container) to the docker-maven-plugin configuration.
This defaults to 0 in docker. Therefore, for the process running inside there is no change of a proper shutdown, when receiving SIGTERM.
In my use case the process writes some log data, when SIGTERM is received before exiting gracefully.
With the current docker-maven-plugin this file is empty.
I extended docker-maven-plugin in a fork and it is working fine there.
The text was updated successfully, but these errors were encountered:
Fixed with merge of #294
Sorry, something went wrong.
No branches or pull requests
I would like to expose the t parameter of the stop call (see https://docs.docker.com/reference/api/docker_remote_api_v1.20/#stop-a-container) to the docker-maven-plugin configuration.
This defaults to 0 in docker. Therefore, for the process running inside there is no change of a proper shutdown, when receiving SIGTERM.
In my use case the process writes some log data, when SIGTERM is received before exiting gracefully.
With the current docker-maven-plugin this file is empty.
I extended docker-maven-plugin in a fork and it is working fine there.
The text was updated successfully, but these errors were encountered: