-
Notifications
You must be signed in to change notification settings - Fork 1.3k
remounting overlayfs fails #2528
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
Comments
The inability to reconfigure overlayfs seems to be intentional: It never did anything but when using the new API it actively throws an error. |
I think it would be reasonable for mount -o remount,lowerdir=/something/new to error rather than silently do nothing but it's definitely surprising to me that remount,rw or remount,ro would fail. (It's probably not strictly necessary to call those in the boot process that's currently failing but it's definitely breaking something that used to work) |
The best way forward would probably be to make sure to only set filesystem options that are not already set to the same value. |
Not sure if I see an error there. man mount:
And note there is also --options-mode <ignore, append, prepend, replace> to work wit options from fstab/mtab. |
Please let's continue the discussion on #2576 to keep it all in one place. |
I found this digging in to https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2037417 where I thought something a bit deeper around an overlayfs that was using paths no longer available from the current mount namespace was going on, but no:
The failure seems to be this syscall:
The text was updated successfully, but these errors were encountered: