- Podman - Podman List Archives

Podman v5.3.2 Released
by Do Not Reply 22 Jan '25

22 Jan '25

Hi all, Podman v5.3.2 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.3.2 Release Notes: -------------- ### Security - This release contains Buildah v1.38.1 which addresses [CVE-2024-11218](https://github.com/advisories/GHSA-5vpc-35f4-r8w6) ### Bugfixes - Fixed a bug where Quadlet `.build` files could create an invalid podman command line when `Pull=` was used ([#24599](https://github.com/containers/podman/issues/24599)). - Fixed a bug where the Mac installer did not install the Podman manpages ([#24756](https://github.com/containers/podman/issues/24756)). ### Misc - Updated Buildah to v1.38.1 - Updated the containers/common library to v0.61.1 - Updated the containers/storage library to v1.56.1 - Updated the containers/image library to v5.33.1 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Assigned ip address does not respond
by Michael Ivanov 14 Jan '25

14 Jan '25

Hallo, I'm trying to set up a container with fixed ip address. I have done the following: podman network create --subnet 10.89.16.0/24 testnet podman run . . . . --network testnet --ip 10.89.16.32 --publish 9094:9092 . . . . . Inside my container a service is listening on port 9092. When I exec into container, I can access service at port 9092 But when I'm trying to connect to 10.89.16.32:9094 from the host, connection hangs. 10.89.16.32 also cannot be pinged from host. When I inspect the network I get the following: island:other [master]> podman network inspect testnet | more [ { "name": "testnet", "id": "0fc4c960a787386f000c94760c47a27bf987e8c7900015a17686f1d49386764b", "driver": "bridge", "network_interface": "podman8", "created": "2025-01-13T23:12:33.065307139+03:00", "subnets": [ { "subnet": "10.89.16.0/24", "gateway": "10.89.16.1" } ], "ipv6_enabled": false, "internal": false, "dns_enabled": true, "ipam_options": { "driver": "host-local" }, "containers": { "20186a8598e92c5dea05d722f46651aa688543ee01cf6aa7a324e55ff631f0ee": { "name": "test", "interfaces": { "eth0": { "subnets": [ { "ipnet": "10.89.16.32/24", "gateway": "10.89.16.1" } ], "mac_address": "ca:60:49:9b:66:e8" } } } } } ] podman version is 5.3.1 (debian/sid), container is run in rootless mode. Best regards, -- Michael Ivanov

2 1

Point of Contact | Deployment of Podman for an Entrerprise
by Raffaele Marchisella 07 Jan '25

07 Jan '25

is there any way I can talk directly with a member of the team at Podman? I would like to talk about the deployment of podman for about 50-100 software engineers in an enterprise environment and how would that look like, if there should be any concerns to know about. I'm open to have a meeting from 6th January and on, too. Best regards, [image: sennder Italia] Raffaele Marchisella IT Specialist raffaele.marchisella(a)sennder.it sennder Italia S.r.l. | Via Arbe 49｜20125 Milan｜Italy Registration no. REA 2567362 Website <https://www.sennder.com> | LinkedIn <https://www.linkedin.com/company/sennder-gmbh/> | Youtube <https://www.youtube.com/channel/UC_7RxMt6tRsGgl5BVXw9OWA> We are hiring – check our open positions HERE! <https://www.sennder.com/career/> Please find sennder's Privacy Policy HERE! <https://www.sennder.com/privacy-policy> Società soggetta all'attività di direzione e coordinamento di sennder Technologies GmbH. Company subject to the management and coordination activities of sennder Technologies GmbH. <https://on.sennder.com/3WEBGak>

3 2

January 7, 2025 Podman Cabal meeting at 11:00 am EST (UTC-5) Canceled!
by Tom Sweeney 06 Jan '25

06 Jan '25

Hi All, Due to a lack of topics and folks trying to recover from the holidays, we are canceling the Podman Cabal meeting scheduled for tomorrow, Jan 7, 2025, at 11:00 a.m. EST (UTC-5). The Cabal will meet next on March 4, 2025, at 11:00 a.m. EST (UTC-5). The Podman Community Meeting will meet on Tuesday February 4, 2025 at 11:00 a.m. EST (UTC-5). If you would like to add a Topic to either meeting, please do so on the agendas, which are linked below by signature. As a reminder, the Community meetings are used for more Demo related topics, while the Cabal is for Design and Planning topics. Happy New Year! t Podman Cabal Agenda: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both Podman Community Meeting Agenda: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both

1 0

shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day 12 Dec '24

12 Dec '24

"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

4 5

Ask Me Anything! Podman, bootc, Podman Desktop, CNCF - Tuesday, December 10, 2024, 10:00 a.m. EST (UTC-5)
by Tom Sweeney 04 Dec '24

04 Dec '24

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

1 0

FreeBSD Podman Machine for FreeBSD containers
by Chris Jones 27 Nov '24

27 Nov '24

Good afternoon, I’m just getting my feet wet with Podman and curious if anyone is running a FreeBSD Podman Machine to run FreeBSD containers. I’m particularly interested in running containers under macOS (my workstation). I know that a lot of recent work has gone into making OCI FreeBSD native container images for the latest release candidate for FreeBSD 14.2 located here: https://download.freebsd.org/releases/OCI-IMAGES/14.2-RC1/aarch64/Latest/ There is progress being made in running Podman containers on FreeBSD with information here: https://freebsdfoundation.org/blog/advancing-cloud-native-containers-on-fre… Cheers, -Chris

1 0

Podman pulls image every time --build is passed to compose on Mac
by Mehdi Haghgoo 24 Nov '24

24 Nov '24

I was expecting Podman to avoid pulling images again every time I run "docker-compose up --build" on Mac (Apple Silicon). I only want the new Python dependencies (in requirements.txt) to be added to the container image, but don't see the necessity of pulling the 200MB image once again each time. Is this expected behavior? Here's my Containerfile: FROM docker.io/library/python:3.12 COPY . /app WORKDIR /app RUN pip install -r requirements.txt CMD ["python", "app.py"]

1 0

Podman v5.3.1 Released
by Do Not Reply 21 Nov '24

21 Nov '24

Hi all, Podman v5.3.1 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.3.1 Release Notes: -------------- - Fixed a bug where the `--ignition-path` option to `podman machine init` would prevent creation of necessary files for the VM, rendering it unusable ([#23544](https://github.com/containers/podman/issues/23544)). - Fixed a bug where rootless containers using the `bridge` networking mode would be unable to start due to a panic caused by a nil pointer dereference ([#24566](https://github.com/containers/podman/issues/24566)). - Fixed a bug where Podman containers would try to set increased rlimits when started in a user namespace, rendering containers unable to start ([#24508](https://github.com/containers/podman/issues/24508)). - Fixed a bug where certain SSH configurations would make the remote Podman client unable to connect to the server ([#24567](https://github.com/containers/podman/issues/24567)). - Fixed a bug where the Windows installer could install WSLv2 when upgrading an existing Podman installation that used the Hyper-V virtualization backend. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

December 3, 2024 Podman Community Meeting Cancelled!
by Tom Sweeney 20 Nov '24

20 Nov '24

Hi All, Most of the regular attendees have other commitments, so we are canceling the December 3, 2024 Podman Community Meeting. The Podman Community Meeting will meet next on Tuesday, February 4, 2025 at 11:00 a.m EST (UTC-5), and the Podman Cabal meeting on Tuesday January 7, 2025 at 11:00 a.m. EST (UTC-5). Hope to see you there! t Agenda: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both

1 0