-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: rootless build with podman #914
Comments
init_buildsystem should not try to create devices if they are already present thanks to container engine. Additionally, it would be nice to support vm-type=podman so we don't need to install podman-docker. |
FWICT
|
Filed as openSUSE/osc#1410 |
On Mon Sep 18, 2023 at 2:15 PM CEST, Fabian Vogt wrote:
> `osc` just needs to learn that `--vm-type=podman` does not need elevated privs.
Filed as openSUSE/osc#1410
How does this relate to the similar problem of running `osc
build` from *inside* of a podman container (e.g., from distrobox
container on MicroOS-base system)?
|
I haven't tried. In theory if everything is set up to allow running nested podman, it might just work. |
it is usually easier to just have a symlink to distrobox-host-exec to /usr/local/bin/podman in the distrobox container ;) |
Solved by openSUSE/osc#1415 |
I probably do something wrong, but in non-root container (at 19d1bab7) I get this:
What am I missing? |
When I remove
|
I'm also having trouble with the current version in openSUSE:Factory:
With --nopreinstallimage:
|
The preinstallimage part should be fixed by osc #1444 already. The podman error could be a regression by the switch to crun? |
Yes, confirmed. It breaks after |
Excellent, thanks! |
A better workaround is to set the runtime back to runc in I'm looking at resolving there issue with crun or maybe converting the default back. |
I get a problem with for i in 1 2 ; do
osc build --vm-type=podman --noservice --clean standard
done that says
and if I manually
|
I can not confirm this issue with tumbleweed. does "osc wipe" help? |
Even after
|
Podman is a container engine that supports rootless containers.
obs-build could leverage this to allow for building packages without root privileges. Conveniently there's also Docker emulation available (
zypper in podman-docker
), so you could reuse the existing Docker support.In fact it partially works already:
→ A rootless podman container is created and runs for a while...
Some bits are still failing, e.g. the creation of device nodes:
What do you think?
The text was updated successfully, but these errors were encountered: