This request is superseded by
request 1036692
(Show diff)
You're not reviewing the full diff of
request 1036431
, but the diff to the superseded
request 1035867
(Show full diff)
Overview
Request 1036431 superseded
- add container-storage-driver.sh (bsc#1197093)
- postinstall script: slight cleanup, no functional change
- Created by dirkmueller
- In state superseded
-
Package maintainers:
dancermak and
danishprakash
- Supersedes 1035867
- Superseded by 1036692
Loading...
Request History
dirkmueller created request
- add container-storage-driver.sh (bsc#1197093)
- postinstall script: slight cleanup, no functional change
dirkmueller superseded request
superseded by 1036692
Shouldn't this be in
/usr/etc/profile.d/?moved there
This might override whatever the user set in
~/.config/containers/storage.confI can make it only set it when there is no config file (it really only matters until you have pulled the first container anyway)
AFAIK the
vfsdriver is "mostly for debugging" or something like thatI believe you're right, yup
According to https://docs.docker.com/storage/storagedriver/select-storage-driver/ the decision matrix for deciding the right storage driver for rootless should be something like this
IF filesystem=btrfs overlayfs driver = btrfs
ELSE IF filesystem=ext4|xfs (ftype=1) THEN driver = overlay|overlay2
ELSE driver= fuse-overlayfs
there is a different decision logic for rootless, as fuse-overlayfs is never chosen, but vfs instead.
anyway, forced it to overlayfs. if overlayfs don't work the user then has to know that they have to set "vfs" explicitly.