# in environment ?
by lejeczek
Hi guys.
Do you use # in your envs?
I wonder if it's just me having issues with those.
For a test, to reproduce the issue, 'ghost' web solution
would be easy & quick:
-> $ podman run -dt ...................... --env
database__client=mysql --env
database__connection__host=11.1.0.1 --env
database__connection__user=ghostadm --env
database__connection__password='xyz#admghost' --env
database__connection__database=ghost_xyz --env
url=https://ghost.xyz
So far all I've tried with 'database__connection__password'
failed, quoting &| escaping.
I often use # - does anybody have a way to make it work?
many thanks, L.
4 months
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.
5 months, 1 week
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 year
Podman v4.9.4 Released!
by Matt Heon
Hi all,
Podman v4.9.4 has been released. This is a patch release for Podman v4
including the fix to CVE-2024-1753, which was already released with Podman
5.0.0. It is provided for the convenience of distributions that cannot
switch to Podman v5 as it is a major version bump (e.g. Fedora versions 38
and 39). It is likely that this will be the last Podman v4 release; we
expect all further development to be on Podman v5.0.
You find more details in the release page on Github here:
https://github.com/containers/podman/releases/tag/v4.9.4
Thanks,
Matt Heon
1 year, 8 months
DevConf.US 2024 CfP Now Open!
by Tom Sweeney
Hi Everyone,
We are excited to announce that the 6th annual DevConf.US CfP
<https://pretalx.com/devconf-us-2024/cfp>[1] is currently open! Head to
DevConf.US <http://devconf.us>[2] to submit your talks, workshops, and
discussion abstracts, along with meet-ups, BoF's, community booth
proposals and really, anything else you are excited to share with the
community! Checkout the website <http://devconf.us>[2] for more details
and topics that we are looking for this year.
The conference will be held from August 14th to 16th 2024 at Boston
University in Boston, MA. We can’t wait to see you there!
Note: The deadline for submissions is April 8, 2024.
Help us get the word out on social media:
*
Follow @devconf_usand retweet all the tweets!
*
Follow us on instagram @devconf_usand share our posts!
*
Follow us on LinkedIn: https://www.linkedin.com/company/devconf-us/
<https://www.linkedin.com/company/devconf-us/>
*
Or tag us in your posts and tweets and we will republish!
Please send questions, comments, and concerns to info(a)devconf.us
<mailto:info@devconf.us>.
Looking forward to all your awesome proposals!
Best regards,
The DevConf.US Crew
@DevConf_US #definefuture
[1]: https://pretalx.com/devconf-us-2024/cfp
<https://pretalx.com/devconf-us-2024/cfp>
[2]: http://devconf.us <http://devconf.us>
1 year, 8 months
Note: Podman v5 container image
by Chris Evich
For users wanting to try out Podman 5 via a container: A stable,
official image should be available shortly after the release of Fedora
40. At this time, we anticipate that to be sometime in late April,
though the date can change unannounced.
If you'd like to try out an experimentation-grade upstream Podman 5,
there is an image (built daily) available today:
quay.io/podman/upstream:latest
1 year, 8 months
Podman v5.0.0 Released
by Matt Heon
Hi all,
Podman v5.0.0 has just been released. This is our first major version bump
in two years, and comes with a large number of new features and swapped
defaults, including a complete rewrite of `podman machine` to improve
stability and performance. Full details are available in the release notes
[1].
We've been working on 5.0 for months now and are excited to get it out into
people's hands. Try it out and let us know what you think!
Thanks,
Matt Heon
[1] https://github.com/containers/podman/releases/tag/v5.0.0
1 year, 8 months
Accessing exposed ports from containers
by Bjoern Franke
Hi,
I'm trying to run a gitea runner with an exposed port where a caching
server listens. Dynamically spawned containers want to connect on
<hostip>:<exposedport> and get a timeout.
The port is exposed in the common way (mapping <extport>:<intport> in
docker-compose.yml) and accessible on the external IP from outside.
Host-OS is Arch, networking via netavark, default bridge setup and
podman 4.9.3.
I'm wondering why the containers can't connect to the exposed port on
the host while external connections are possible.
Regards
Bjoern
1 year, 9 months
image repository for podman
by Harish Gaddale
Hi All,
I am new to podman. Pardon if this question is an obvious one.
To pull docker images, we go to docker registry / hub : https://hub.docker.com
Is there a podman registry or hub where we could find all the podman images?
If there is no special registry or hub, what is the reason for that?
Thank You
Harish Gaddale
1 year, 9 months
