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
1 week, 2 days
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.
10 months, 3 weeks
mqueue msg_max in rootless container
by Michael Ivanov
Hallo!
I'm trying to run my application in podman rootless container and I stumble
on following problem: my program needs /proc/sys/fs/mqueue/msg_max to be at
least 256, but in running container this value is just 10. When I try to
specify this parameter while running the image (--sysctl 'fs.mqueue.msg_max=256')
I get the following error:
Error: open /proc/sys/fs/mqueue/msg_max: Permission denied: OCI permission denied
and container is not created.
My host where container is being run has this parameter set to 256. How can I
expose current host setting for msg_max to my container?
Best regards,
--
\ / | |
(OvO) | Михаил Иванов |
(^^^) | |
\^/ | E-mail: ivans(a)isle.spb.ru |
^ ^ | |
1 year
Re: $TMPDIR in rootless_storage_path?
by Daniel Walsh
On 10/11/23 15:22, Rahaman, Ronald O wrote:
>
> I’ve read that the rootless_storage_path setting interprets $HOME and
> $UID. Does it interpret $TMPDIR or any other variables?
>
Podman uses $TMPDIR if set, but this has nothing to do with the
rootless_storage_path.
>
> Thanks,
>
> Ron
>
> --------
>
> Ron Rahaman
>
> Research Scientist II, Research Software Engineer
>
> Partnership for an Advanced Computing Environment (PACE)
>
> Georgia Institute of Technology
>
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
1 year, 2 months
$TMPDIR in rootless_storage_path?
by Rahaman, Ronald O
I’ve read that the rootless_storage_path setting interprets $HOME and $UID. Does it interpret $TMPDIR or any other variables?
Thanks,
Ron
--------
Ron Rahaman
Research Scientist II, Research Software Engineer
Partnership for an Advanced Computing Environment (PACE)
Georgia Institute of Technology
1 year, 2 months
Generate quadlet unit files with podman
by Mehdi Haghgoo
What I have learned from docs so far is that podman cannot generate quadlet unit files, and those need to be written manually. Isn't this inconvenient? I prefer the former " generate aystemd" but it's deprecated.
Am I wrong?
1 year, 2 months
Generate quadlet unit files with podman
by mahdi-haghgoo＠live.com
What I have learned from docs so far is that podman cannot generate quadlet unit files, and those need to be written manually. Isn't this inconvenient? I prefer the former " generate aystemd" but it's deprecated.
Am I wrong?
1 year, 2 months
buildah bud vs podman build
by Leon Fauster
Hi all, I'm doing my first steps with podman and friends - so,
bear with me.
I was expecting the same results between buildah bud vs
podman build while creating an image with a Containerfile.
I noticed that the podman's artifact has a layer more then
buildah's one:
podman:
"Data": {
"LowerDir": "...1ef8/diff",
"UpperDir": "...2a81/diff",
"WorkDir": "...2a81/work"
}
buildah:
"Data": {
"UpperDir": "...b9918/diff",
"WorkDir": "...b9918/work"
}
Podmans additional layer has the outcome of:
RUN adduser --no-create-home --home-dir /app --shell /bin/bash -u 1000 user
separated while buildah has merged it into the "base".
Is this the normal behavior or which knob should I use for a consistency
output?
--
Thanks,
Leon
1 year, 2 months
