You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned here: ostreedev/ostree#2640 (comment)
ignition would like to be able to track which block devices as used by a mount. We can't currently always do this. For example, the mount source is a relative pathname. We should maybe make this an absolute pathname?
There might be similar issues with the basedir.
The text was updated successfully, but these errors were encountered:
We do expose all the backing paths in the mount info, although they are relative if they were supplied relative. I looked at other stuff, and nothing in the current kernel seems to change given options to absolute paths when printed. Maybe we just need to be careful about passing important mount options by full paths when we mount stuff.
I think this is not necessary; in general, we just need to teach tooling to look at the underlying physical root filesystem, which is done in coreos/coreos-installer#1203
As mentioned here: ostreedev/ostree#2640 (comment)
ignition would like to be able to track which block devices as used by a mount. We can't currently always do this. For example, the mount source is a relative pathname. We should maybe make this an absolute pathname?
There might be similar issues with the basedir.
The text was updated successfully, but these errors were encountered: