cmd/initContainer: Do not try to remount /etc/machine-id as ro#1354
cmd/initContainer: Do not try to remount /etc/machine-id as ro#1354debarshiray merged 2 commits intocontainers:mainfrom
Conversation
|
Here's the error I was getting ftr: and here's what my mounts look like: And a link to the issue when found out |
|
I am not entirely sure about the fix, since |
1fc4c7b to
24e5365
Compare
|
That's odd. The CentOS Stream 9 and Fedora tests on Zuul CI didn't run. |
|
recheck |
|
Build failed. ❌ unit-test RETRY_LIMIT in 32s |
There was a problem hiding this comment.
Thanks for tracking this down, @alatiera ! The patch looks good to me.
I have only one question about the root cause. It seems to me that on this particular build of GNOME OS, the entire / on the host is mounted with ...,nodev,.... Since /etc isn't a separate mount point, /etc is also nodev, and this runs into problems with the ro flag as it's used here. ie., mount --rbind -o ro /run/host/etc/machine-id /etc/machine-id tries to remove that nodev and fails. Did I understand that right?
|
That's my understanding as well. Only |
containers#1330 Signed-off-by: Nieves Montero <nmontero@redhat.com>
24e5365 to
3ed0af5
Compare
On new builds of GNOME OS [1], the host's / is mounted with 'nodev,...' and those flags are also inherited by /etc because it's not a separate mount point. This leads to the same problem with /etc/machine-id that was seen before with /var/lib/flatpak, /var/lib/systemd/coredump and /var/log/journal [2]. Therefore, use the same approach [2] to handle /etc/machine-id. [1] https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/718 [2] Commit 1cc9e07 containers@1cc9e07b7c36fe9f containers#1340 containers#911 containers#1354 Signed-off-by: Jordan Petridis <jordan@centricular.com>
3ed0af5 to
219f5b4
Compare
Thanks for confirming that! I took the liberty to add that to the commit message, because I will surely mix up the details very soon. :) Let's wait for the CI to finish. Note that the tests run on Fedora Rawhide nodes are failing because of the same reasons as in #1344 and #1331 , and the root cause appears to be |
|
Build failed. ❌ unit-test RETRY_LIMIT in 33s |
Followup to 1cc9e07
Sometimes the parent location might be mounted with nosuid,nodev,noexec and trying to remount it as ro would remove those and thus fails.
See commit mentioned above for more details.
#911