RunRoot & mistaken IDs
by lejeczek
Hi guys.
I experience this:
-> $ podman images
WARN[0000] RunRoot is pointing to a path
(/run/user/1007/containers) which is not writable. Most
likely podman will fail.
Error: creating events dirs: mkdir /run/user/1007:
permission denied
-> $ id
uid=2001(podmania) gid=2001(podmania) groups=2001(podmania)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
I think it might have something to do with the fact that I
changed UID for the user, but why would this be?
How troubleshoot & fix it, ideally without system reboot?
many thanks, L.
2 days, 7 hours
shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day
"man podman-build" suggests that the context argument is optional:
SYNOPSIS
podman build [options] [context]
podman image build [options] [context]
...
If no context directory is specified, then Podman will assume
the current working directory as the build context, which
should contain the Containerfile.
but if i have a directory with nothing but a Containerfile, i get:
$ podman build
Error: no context directory specified, and no containerfile specified
$
OTOH, specifying context of current directory:
$ podman build .
STEP 1: FROM alpine:latest
... etc etc ...
thoughts?
rday
6 months, 3 weeks
Ask Me Anything! Podman, bootc, Podman Desktop, CNCF - Tuesday, December 10, 2024, 10:00 a.m. EST (UTC-5)
by Tom Sweeney
Hey All!
Did you hear that Podman, bootc and Podman Desktop are moving to CNCF?
Do you have questions on that or anything else container-related? Ask
your questions at the "Ask Me Anything" session next Tuesday, December
10, 2024, at 10:00 am EST (UTC-5). Details including the conference link
on this blog post:
https://blog.podman.io/2024/12/podman-bootc-podman-desktop-ama/
<https://blog.podman.io/2024/12/podman-bootc-podman-desktop-ama/>
Hope to see you there!
t
7 months