-
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
[Bug]: Unable to hijack connection with trace log enabled in server mode #17332
Comments
Update: it's no longer latest upstream release as 4.4 got released today. |
Tested with 4.4 and... it works! Will there be a backport to 4.3 or will 4.4 be released for Fedora 37? |
Thanks for reaching out and testing, @Agalin. Podman 4.4 will be released to Fedora 37 soon. Since it's already fixed, I am going to close the issue. Again, thanks for checking! |
@vrothberg I ran into the same issue on 4.4.2
|
@hsnoil, thanks for reaching out. Please open a new issue with the reproducer. |
Issue Description
When you run Podman server (local, through unix socket) with log level set to
trace
it fails to start a container. Podman client ends withError: unable to hijack connection
.When you run the same container with same options directly (without using remote) it starts properly with
trace
log level.Steps to reproduce the issue
Steps to reproduce the issue
--log-level=trace
(podman --log-level=trace system service
)CONTAINER_HOST
env variable.podman run --rm -ti fedora
.Describe the results you received
podman run
command fails withError: unable to hijack connection
.In server logs it seems to have problem with container runtime initialization:
Full log
Describe the results you expected
Container starts using remote server like it starts when running directly.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Podman 4.3.1 rootless on Fedora 37 running in a VM. SELinux enabled.
Server configured through user-level systemd service triggered by user-level systemd socket (default config available with Fedora with log level changed).
Changes in containers.conf
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: