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, 5 days
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
Support for WireGuard interface and multiple network interfaces
by Maximilian Ehlers
Helo everyone,
for a while I have been using containers that join themselves into a
VPN via their entrypoint script.
Only a small CIDR is forwarded to that private network and all other
traffic gets routed over the bridged network via the host.
In my exact use case the containers use WireGuard and need the
following configurations:
- private key (public keys can be derived)
- public key of an endpoint
- network routable IP of an endpoint
- Port of the endpoint
- CIDR to route to endpoint
Optionally multiple endpoints could be specified.
As this hack inside the entrypoint is not the most elegant way (DRY)
and so on, I would like to ask whether or not it would be possible to
integrate this functionality into podman.
Specifically to integrate support for a WireGuard interface
configurable via CLI flags/config && together with this giving a
container multiple network interfaces at spawn with the ability to
specify which CIDR should route to which interface.
Implementing this would be an interesting challenge for me if it is at
all possible (or am I wasting my time here?)/
Any hints as to how I could proceed in implementing and testing this in
a fork of the project would be much appreciated!
Thanks alot
Max <b-m-f>
3 years, 1 month
Podman Community Cabal Meeting Time Change and Podman Community Meeting reminder
by Tom Sweeney
Hi All,
Just a quick note on a couple of meeting updates. The Podman
Community Cabal Meetings have been happening at 10:00 a.m. EDT (UTC-4)
on the third Thursday of each month. Due to a conflicting meeting for a
number of the key maintainers, we have decided to move the meeting from
10:00 a.m. to 11:00 a.m. EDT, still on the third Thursday of the month.
Secondly, the next Podman Community Meeting snuck up on me and is
happening this coming Tuesday November 2, 2021 at 11:00 a.m. EDT
(UTC-4). We don't have a lot of topics for next week, so if you have
something you'd like to present, or a topic that you'd like to hear
about, please drop me a note.
Thanks All!
t
3 years, 1 month
is podman (and friends) reasonably complete under recent ubuntu?
by Robert P. J. Day
current colleague wants to set up as complete a podman-based
environment as possible, and corporate policy dictates must be ubuntu,
but can be as recent an ubuntu version as desired (even brand new
21.10).
predictably, i suggested fedora would be a better choice, but that's
not an option given corporate choice of ubuntu for dev boxes. so the
question is, will that still provide a reasonably complete set of
container tools relative to fedora using just standard packages?
rday
3 years, 1 month
Q: Slightly uncomplicating manifest-lists
by Chris Evich
All,
Recently I wrote a blog article that touches on a few podman (and
buildah) commands which are bound to catch people off-guard:
https://podman.io/blogs/2021/10/11/multiarch.html
Unfortunately the reason for the "Ugh! What? Really?" of 'rm' and 'push'
is "maintaining compatibility" - hence, unlikely to change. See
https://github.com/containers/podman/issues/11899
So my thinking was, if we can't change the CLI can we make the feedback
to users better? At least then, people would be alerted when it comes
to surprising 'rm'/'push' behavior. For example:
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/redis latest 7faaec683238 7 days 116 MB
reg.fed.org/fedora 34 191682d67252 2 weeks 184 MB
ex.co/foo/bar latest [M]123456576b54 1 second 123 GB
reg.acc.red.c/ubi8-init latest 670b0e87da3c 4 weeks 251 MB
quay.io/libpod/alpine latest 961769676411 2 years 5.85 MB
Indicating 'ex.co/foo/bar' is a manifest list not a regular image, and
so needs special handling by the user. Alternatively it could be it's
own column. I was just wanted to be sensitive to anyone who may be
scraping the space-separated data for some purpose.
What are your opinions/concerns/alternatives for something like this?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
3 years, 2 months
Container documentation
by Michael Ivanov
Hallo,
One small question strictly not related to podman: are there any means
to bundle container-related documentation to container itself, similar
to perl's embedded POD) and to query it in some generic way?
(say like 'podman docs <container name>')?
Best regards,
--
\ / | |
(OvO) | Михаил Иванов |
(^^^) | |
\^/ | E-mail: ivans(a)isle.spb.ru |
^ ^ | |
3 years, 2 months