Kapsule dosent work on KDELinux 06-06-2026

[king@workstation:~] [1] $ kapsule create --image images:opensuse/tumbleweed --nvidia-drivers --no-mount-home --custom-mounts ‘/home/ai:/home/king/Ai’ AiTumblewee
d
Creating container: AiTumbleweed
Ensuring image is cached locally…
Image: images:opensuse/tumbleweed
NVIDIA userspace drivers will be injected on start
Creating container…
Masking systemd-networkd-wait-online.service (host networking)
No /.kapsule/init/ directory — skipping init scripts
Syncing host configuration (timezone, locale, DNS)
Warning: Could not set cap_setuid+ep on /usr/bin/newuidmap: Error: Command not found
Warning: Could not set cap_setgid+ep on /usr/bin/newgidmap: Error: Command not found
Configured rootless Podman (cgroup_manager=cgroupfs)
✓ Container ‘AiTumbleweed’ created successfully
✓ Container created

Your log does not show Kapsule failing.

The container creation completed successfully, including image preparation, host configuration synchronization, rootless Podman configuration, and final container creation. The only warnings shown are related to missing “newuidmap” and “newgidmap” binaries, which are typically used for user namespace UID/GID mapping in rootless container environments.

Those warnings are not fatal in this case because Kapsule continued execution and Podman was configured successfully afterwards. The decisive part of the log is the end result:

✓ Container ‘AiTumbleweed’ created successfully
✓ Container created

Based on the output provided, Kapsule is working. What the log actually indicates is an incomplete rootless container environment where the UID/GID mapping helpers are unavailable. That may reduce functionality depending on the workload, but it is not evidence of a failed container creation.

The title is therefore misleading. The posted output demonstrates a successful create operation with non-fatal warnings, not a Kapsule failure.

It looks very much like this issue though:

You can see there that the user went on to attempt kapsule enter, which failed - so there is a genuine issue here.

There’s a bug ticket for this on KDE Invent.

The warnings suggest more that /usr/bin/setcap is the missing (or for some reason not findable) binary.

If /usr/bin/newuidmap was missing, the error would be Failed to set capabilities ... No such file or directory, rather than Command not found.

I filed that issue. it is the same.