Feb 03 09:33:48 xxxxx.yyy.siemens.net kernel: overlayfs: maximum fs stacking depth exceeded
Feb 03 09:37:48 xxxxx.yyy.siemens.net kernel: overlayfs: maximum fs stacking depth exceeded
during run of docker images we face this error, any suggestion how to fix that without compiling the kernel ourselves ?
it occurs already when we run ‘docker run hello-world’ …, we do have of course more concrete docker images that do real work where we have seen that recently
At least on my end, on a freshly installed Fedora CoreOS 41.20250105.3.0 and 41.20250117.3.0 in a virtual machine, executing sudo docker run hello-world produces the expected result.
Yes, there are no errors, but as I already mentioned, this is a freshly provisioned virtual machine.
sudo docker run hello-world
core@143838-vm:~$ sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
e6590344b1a5: Pull complete
Digest: sha256:d715f14f9eca81473d9112df50457893aa4d099adeb4729f679006bf5ea12407
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
core@143838-vm:~$ rpm-ostree status
State: idle
AutomaticUpdatesDriver: Zincati
DriverState: active; periodically polling for updates (last checked Mon 2025-02-03 10:50:31 UTC)
Deployments:
● fedora:fedora/x86_64/coreos/stable
Version: 41.20250117.3.0 (2025-01-31T20:20:40Z)
Commit: e3584d6918d0bcb7e73e03dd05b1fb1ebd8fee1d8e2a417a9535ee931b0885ae
GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
fedora:fedora/x86_64/coreos/stable
Version: 41.20250105.3.0 (2025-01-21T00:57:04Z)
Commit: 30901bf3917665804d37f363ac2a6a914a01550e19436735ae5456c52f179ea0
GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
my is also a fresh one from today 10:00 with the newest stable 41.20250117.3.0 , after rollout (via ignition method to add these and that for our company demands) we quickly checked how it behaves with that overlayfs, cause we say the same error in some older versions too
ok, we need to double check more if there is really functionality degraded or failing
For reference, this is the Butane config I used to provision the machine.
143838.yaml
# Ignition Config for VM
variant: fcos
version: 1.6.0
# Authentication
passwd:
users:
- name: core
password_hash: $y$...
ssh_authorized_keys: [ssh-ed25519 AAAA...]
storage:
disks:
# Configure VM virtual disk vda.
# The link to the block device the OS was booted from.
- device: /dev/disk/by-id/coreos-boot-disk
# We do not want to wipe the partition table since this is the primary device.
wipe_table: false
partitions:
- number: 4
label: root
# Allocate at least 8 GiB to the rootfs.
size_mib: 8192
resize: true
- label: var
size_mib: 0
# Configuring the filesystems
filesystems:
- device: /dev/disk/by-partlabel/root
wipe_filesystem: true
format: btrfs
label: root
- path: /var
device: /dev/disk/by-partlabel/var
format: btrfs
with_mount_unit: true
label: var
files:
- path: /etc/hostname
mode: 0644
contents:
inline: 143838-vm.local
# systemd units
systemd:
units:
# Add a systemd dropin to override the default serial-getty@ttyS0.service.
# The override will make the service automatically log the core user in to the
# serial console of the booted machine.
- name: serial-getty@ttyS0.service
dropins:
- name: autologin-core.conf
contents: |
[Service]
# Override Execstart in main unit
ExecStart=
# Add new Execstart with `-` prefix to ignore failure`
ExecStart=-/usr/sbin/agetty --autologin core --noclear %I $TERM