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
When container-storage-setup is run it fails with:
ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend; consider different driver or separate volume or OS reprovision
The message is correct insomuch that /var is on a partition with ftype=0, but I have mounted /var/lib/docker from a partition which has ftype=1 which allows docker to start without the ftype warnings. Shouldn't container-storage-setup also be using /var/lib/docker and not /var when testing for ftype?
The text was updated successfully, but these errors were encountered:
I guess we could. /var/lib/docker is not present when run for the first time. We could improve it to first check for /var/lib/docker otherwise fall back to check on /var.
Would it be better to test /var/lib before testing /var as it is conceivable that it could be being mounted from a different filesystem than /var. Is there any risk of /var/lib not existing on a system?
When container-storage-setup is run it fails with:
ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend; consider different driver or separate volume or OS reprovision
The message is correct insomuch that /var is on a partition with ftype=0, but I have mounted /var/lib/docker from a partition which has ftype=1 which allows docker to start without the ftype warnings. Shouldn't container-storage-setup also be using /var/lib/docker and not /var when testing for ftype?
The text was updated successfully, but these errors were encountered: