-
Notifications
You must be signed in to change notification settings - Fork 60
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
systemctl daemon-reload interferes with docker's access to /dev/pts/0 #1321
Comments
Yep, The current version in Fedora is 1.1.3 (see https://src.fedoraproject.org/rpms/runc). Looks like 1.1.4 came out a few months ago. |
Made a PR on update. |
Thanks so much @copperii! |
Whats the status of this. Still the 1.1.3 version is present in all release streams (stable/testing/next). |
The answer is slightly complicated because of the likely Fedora 37 major release coming up next week. It will almost certainly be in the Either way. This issue will be updated when it lands in a release. If you want to try it out today you can grab the latest |
Sorry I had lost track of this one. This landed in the F36 RPM |
The fix for this went into |
The fix for this went into |
The fix for this went into |
I had missed that this one got fixed. See coreos/fedora-coreos-tracker#1321
I had missed that this one got fixed. See coreos/fedora-coreos-tracker#1321
Describe the bug
The version of runc in Fedora CoreOS 36.20220918.3.0 seems to suffer from the bug fixed in [1.1] Fix failed exec after systemctl daemon-reload (regression in 1.1.3) which was released in runc 1.1.4.
Reproduction steps
Expected behavior
I expect both
docker exec
invocations to work identically.Actual behavior
Docker fails to access
/dev/pts/0
aftersystemctl daemon-reload
has been run.System details
Ignition config
Butane file
Additional information
N/A
The text was updated successfully, but these errors were encountered: