-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman 3.0.0 fails to run containers with VOLUME's defined (e.g. postgres or mysql) #9393
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
I am getting the same error as above but for gradle.
|
#9383 will fix |
edigaryev
added a commit
to cirruslabs/cirrus-cli
that referenced
this issue
Feb 16, 2021
edigaryev
added a commit
to cirruslabs/cirrus-cli
that referenced
this issue
Feb 16, 2021
* Work around containers/podman#9390 * Work around containers/podman#9393 * Stream launched container's logs to the CLI's logger * Work around containers/podman#9351 * Ignore bodyclose linter false-positive * .cirrus.yml: run "go test" on Windows verbosely * Use sub-context for the ContainerLogs() call To avoid potential hangs in stdcopy.StdCopy(). * ContainerLogs: use buffered channels To avoid a case when stdcopy.StdCopy() waits for the io.Pipe() to unlock, while the connection from which it reads the logs gets closed. This presumably results in the tail part of the logs getting lost. * TestContainerLogs: skip last line check for Podman
Closing, fixed upstream. Preparing 3.0.1 with the fix now. |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
The text was updated successfully, but these errors were encountered: