diff options
author | Nick Guenther <nick.guenther@polymtl.ca> | 2022-02-28 12:54:09 -0500 |
---|---|---|
committer | Nick Guenther <nick.guenther@polymtl.ca> | 2022-03-01 12:09:42 -0500 |
commit | 572e6464f607189744afb76ee729ab31018266ad (patch) | |
tree | 4a8a8e2fafacc025494d5eb8545d5b729488be3d /cmd/podman/images/diff.go | |
parent | 8bdda91ab738d634528259581c8adebe1db007b4 (diff) | |
download | podman-572e6464f607189744afb76ee729ab31018266ad.tar.gz podman-572e6464f607189744afb76ee729ab31018266ad.tar.bz2 podman-572e6464f607189744afb76ee729ab31018266ad.zip |
Use storage that better supports rootless overlayfs
overlayfs -- the kernel's version, not fuse-overlayfs -- recently learned
(as of linux 5.16.0, I believe) how to support rootless users. Previously,
rootless users had to use these storage.conf(5) settings:
* storage.driver=vfs (aka STORAGE_DRIVER=vfs), or
* storage.driver=overlay (aka STORAGE_DRIVER=overlay),
storage.options.overlay.mount_program=/usr/bin/fuse-overlayfs
(aka STORAGE_OPTS=/usr/bin/fuse-overlayfs)
Now that a third backend is available, setting only:
* storage.driver=overlay (aka STORAGE_DRIVER=overlay)
https://github.com/containers/podman/issues/13123 reported EXDEV errors
during the normal operation of their container. Tracing it out, the
problem turned out to be that their container was being mounted without
'userxattr'; I don't fully understand why, but mount(8) mentions this is
needed for rootless users:
> userxattr
>
> Use the "user.overlay." xattr namespace instead of "trusted.overlay.".
> This is useful for unprivileged mounting of overlayfs.
https://github.com/containers/storage/pull/1156 found and fixed the issue
in podman, and this just pulls in that via
go get github.com/containers/storage@ebc90ab
go mod vendor
make vendor
Closes https://github.com/containers/podman/issues/13123
Signed-off-by: Nick Guenther <nick.guenther@polymtl.ca>
Diffstat (limited to 'cmd/podman/images/diff.go')
0 files changed, 0 insertions, 0 deletions