Util-linux v2.41-1.1 breaks Kubernetes subPath mounts on MicroOS

1

Hi team,

I’m currently running the las version of openSUSE MicroOS, and in this last version I notice that is running util-linux-2.41-1.1.x86_64, and I’m experiencing critical issues in my Kubernetes clusters (specifically with K3s).

The update breaks pods that rely on subPath volume mounts. The affected pods fail with the following error:

vbnet

CopiarEditar

CreateContainerConfigError: failed to prepare subPath for volumeMount

This is affecting multiple critical services, including workloads using emptyDir, ConfigMaps, and custom volume mounts.

Downgrading to a previous snapshot (prior to the update) resolves the issue, confirming that util-linux is the likely cause. Other nodes in my cluster that have not been updated and still run an earlier version (e.g., 2.40.4) do not have this issue.

Steps to reproduce:

  1. Run Kubernetes (K3s) on MicroOS.
  2. Update to util-linux-2.41-1.1.
  3. Deploy a pod that uses a volume with subPath.
  4. Observe failure on container creation.

This appears to be a regression introduced in util-linux-2.41. Other nodes in my cluster still running 2.40.4-4.2 are unaffected and continue to run workloads normally.

Please advise if a fix or rollback is planned for the Tumbleweed repository. This issue makes the latest update incompatible with containerized workloads relying on subPath mounts, which is a serious blocker.

Thank you

2

@pribeiro Hi and welcome to the Forum :smile:
You should be asking at https://forums.opensuse.org but if you think it is a bug, then suggest https://en.opensuse.org/openSUSE:Submitting_bug_reports

1 Like
3

This sounds like https://github.com/k3s-io/k3s/issues/12005 and https://github.com/k3s-io/k3s/issues/12006 - the issue is with util-linux (in openSUSE MicroOS hence @malcolmlewis’s valid comment).

The advice re K3s is to use the --prefer-bundled-bin option as a workaround in the meantime. It’s an experimental option listed at https://docs.k3s.io/cli/server#experimental-options .

4

I have had this Problem as well since last Sunday. The newer util-linux was added on 6th of June. A rollback is a solution, but for anyone who needs these nightly updates could create a snapshot and install an older version of util-linux and lock it. This allows you to get nightly updates without updating util-linux

sudo transactional-update shell
cd /tmp
~~curl -LJO https://download.opensuse.org/history/20250605/tumbleweed/repo/oss/x86_64/util-linux-2.40.4-4.2.x86_64.rpm~~
~~curl -LJO https://download.opensuse.org/history/20250605/tumbleweed/repo/oss/x86_64/util-linux-systemd-2.40.4-4.2.x86_64.rpm~~

sudo rpm -Uvh --oldpackage util-linux-2.40.4-4.2.x86_64.rpm util-linux-systemd-2.40.4-4.2.x86_64.rpm

sudo zypper addlock util-linux
sudo zypper addlock util-linux-systemd

exit

reboot

after reboot and you could check the util-linux version as follows

rpm -qa | grep util-linux

so, after testing I am correcting myself. My suggestion is not working. I am not sure why but only downgrading util-linux is not enough, hence rolling back to 5th of June snapshot looks like the only solution until this bug is fixed