Comment 10 for bug 2009065

Hi, I do think I'm affected by the same issue. Is it still helpful to test the 5.19.0-40.41 kernel as proposed by the kernel bot in the previous message? I don't want to mess up my server, but if it helps getting this fixed faster for 22.04, I'm willing to install the kernel from -proposed.

Currently I'm on 22.04 with the following kernel:
linux-hwe-5.19-headers-5.19.0-38/jammy-security,jammy-updates,now 5.19.0-38.39~22.04.1 all [installed,automatic]

The issue I'm having is with LXD on btrfs when trying to use docker with overlay2 in an unprivileged container.

In the container:
# docker run -it --rm busybox
docker: Error response from daemon: mkdir /var/lib/docker/overlay2/551bd2f3c71ebb9a3d672ac5993d72aea9d58035c0283708e503fc695a131c42-init/merged/proc: read-only file system.
See 'docker run --help'.

Host dmesg:
[ 6344.916322] overlayfs: failed to create directory /var/lib/docker/overlay2/551bd2f3c71ebb9a3d672ac5993d72aea9d58035c0283708e503fc695a131c42-init/work/work (errno: 1); mounting read-only
[ 6344.916340] overlayfs: fs on '/var/lib/docker/overlay2/l/QCM5T4AYJGCEMUPJJKGRKLPDGO' does not support file handles, falling back to xino=off.
[ 6344.916356] overlayfs: POSIX ACLs are not yet supported with idmapped layers, mounting without ACL support.

It seems to be one long sentence, split up in a misleading way. At first I read it as "mounting read-only", but later noticed that it actually states "mounting read-only fs on ..." as if the filesystem contained in the image were read-only by itself, which I'm not sure of.