openwrt / openwrt/packages

podman: issues running applications in containers from non-root accounts

Open
#15,096 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Maintainer: @dangowrt
Environment: x86_64 master

Description:
The podman utility is meant to allow non-root users to run applications in containers. This bug is meant to track things preventing this from working on OpenWrt. (Note there is also ongoing work on uxc.)

  1. The default OpenWrt kernel does not contain support for EXT4 security labels (EXT4_FS_SECURITY), and this seems to cause podman to fail under some circumstances. I reported this upstream, and upstream merged a fix. See issue #9687 and pull request #851. For reference, here is the corresponding error:
Error: error creating container storage: error creating an ID-mapped copy of layer "[hash]": exit status 1: error during chown: storage-chown-by-maps: lgetxattr bin: operation not supported
  1. /etc/containers/* is not readable by anyone but root. Fedora lets non-root users read files in this directory, so we could probably do the same on OpenWrt.

  2. Non-root users cannot write to /sys/fs/cgroup/*. I am not sure how to safely handle this, and I have not yet figured out how other distributions do it. I am still trying to find information about how this is done.

  3. Running podman run ... wants to mount /proc and so on in the container. This fails when run as non-root with:

mounting "/proc" to rootfs at "/proc" caused: operation not permitted

This might be related to the user namespaces, but I am not yet sure of this. I have installed shadow-newuidmap and -newgidmap, and I think I have set /etc/subid and /etc/subgid properly.

  1. /var/tmp does not permit non-root users to write, and it does not bear the sticky bit. Strange.

For reference, I found the following articles helpful for understanding how to build namespaces on Linux:

https://medium.com/@teddyking/linux-namespaces-850489d3ccf
https://medium.com/@teddyking/namespaces-in-go-basics-e3f0fc1ff69a
https://medium.com/@teddyking/namespaces-in-go-user-a54ef9476f2a
https://medium.com/@teddyking/namespaces-in-go-reexec-3d1295b91af8
https://medium.com/@teddyking/namespaces-in-go-mount-e4c04fe9fb29
https://medium.com/@teddyking/namespaces-in-go-network-fdcf63e76100
https://medium.com/@teddyking/namespaces-in-go-uts-d47aebcdf00e

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the non-root failures described for /etc/containers/, /sys/fs/cgroup/, /proc, and /var/tmp on an x86_64 master build, while checking the EXT4_FS_SECURITY kernel setting. Read the linked upstream Podman and containers/storage issues before separating these into actionable fixes. Done would require each identified blocker to have a confirmed OpenWrt-compatible resolution and verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.