- Podman - Podman List Archives

Proposal for Website Updates
by Scott McCarty 20 Sep '21

20 Sep '21

All, I chatted with Mehul today and I want to start a conversation around how we could improve the docs. Here are my thoughts: 1. Figure out a way to keep the main page canonical sources on https://github.com/containers/podman/tree/main/docs/source/markdown 2. Synchronize https://github.com/containers/podman/docs/source/markdown <https://github.com/containers/podman/tree/main/docs/source/markdown> to github.com/containers/podman.io/docs/source/markdown <http://github.com/containers/podman.io/docs> 3. Let's move everything else from github.com/containers/podman/docs <http://github.com/containers/podman/docs/source/markdown> over to the github.com/containers/podman.io/docs 4. Update the theme to this new theme Mehul tested [1] call furo. Feel free to test that container image. It pulls the content from the current repository. 5. If we do #3, we can make it easier for people to commit docs because it wouldn't need to go through the full CI/CD gating tests (might not be correct. Is the podman.io repository gated by the same CI/CD?) 6. Second, we could have dedicated editors instead of engineers approve docs changes An alternative to this proposal could be to use a completely new repository apart from podman.io. If we can separate the docs out, I think we could find volunteers to be editors (aka approve PRs). This would allow core code contributors to focus on code, and docs volunteers to focus on docs. Stated another way, I don't think docs needs CI/CD like code. I think editors probably do a better job (though CI/CD could be useful for link checking, etc). Thoughts? [1]: FROM fedora:latest EXPOSE 8000 RUN dnf install -y gpgme-devel \ libseccomp-devel.x86_64 \ systemd-devel \ make \ git \ golang \ python \ && export PKG_CONFIG_PATH="/usr/lib/pkgconfig" RUN cd / && git clone https://github.com/containers/podman.git \ && cd podman \ && make install.tools RUN cd /podman/docs \ && dnf -y install python3-sphinx python3-recommonmark \ && pip install sphinx-markdown-tables furo \ && sed -i 's|html_theme = "alabaster"|html_theme = "furo"|g' /podman/docs/source/conf.py \ && make html WORKDIR /podman/docs CMD ["python", "-m", "http.server", "8000", "--directory", "build/html"] Best Regards Scott M -- -- 18 ways to differentiate open source products from upstream suppliers: https://opensource.com/article/21/2/differentiating-products-upstream-suppl… -- Scott McCarty Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty(a)redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com

4 4

fluentd log driver?
by Michael Ivanov 16 Sep '21

16 Sep '21

Hallo, Is fluentd log driver available for podman run? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

2 1

Help with Podman API changes
by Rusty Sapper 13 Sep '21

13 Sep '21

Wonder if anyone can tell me what changed with the API from version 3.1.7 ro 3.2.3? We use the jenkins docker plugin to allow jenkins to connect to our Linux nodes and spin up podman containers to run builds in. up till now, everything worked fine. on a new Linux node, we ran an update and it picked up the latest podman version from our RedHat Satellite server. On the older Nodes, this is the version jenkins shows when using the cloud "test connection" button from the cloud/template setup screen. Version = 3.0.2-dev on the new node to that has the newer version of podman, newer version: Version = 3.2.3 However, Jenkins can no longer spin up the containers. here is the error jenkins provides when trying to start a container with the newer version.: Note: Disabled 21 sec ago due to error. Will re-enable in 4 min 38 sec. Reason: Template provisioning failed. com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type `com.github.dockerjava.api.model.Capability` from String "CHECKPOINT_RESTORE": not one of the values accepted for Enum class: [ALL, SYS_BOOT, DAC_OVERRIDE, NET_RAW, BLOCK_SUSPEND, FOWNER, IPC_LOCK, IPC_OWNER, SYS_PACCT, NET_BIND_SERVICE, WAKE_ALARM, FSETID, DAC_READ_SEARCH, SYS_CHROOT, SYS_RAWIO, SYS_ADMIN, KILL, MAC_ADMIN, SYS_RESOURCE, CHOWN, SETPCAP, SYS_PTRACE, NET_ADMIN, SETFCAP, SYS_NICE, LINUX_IMMUTABLE, AUDIT_CONTROL, LEASE, AUDIT_WRITE, SYS_MODULE, MKNOD, SYSLOG, MAC_OVERRIDE, SYS_TIME, SETGID, SETUID, SYS_TTY_CONFIG, NET_BROADCAST] at [Source: (byte[]) the only thing that changed is the newer version of podman. seems like maybe the API is returning some new information of the formatting of the returned info has changed? any help or insights would be greatly appreciated. Thanks, Rusty

2 1

Re: Podman machine & portforwarding
by Brent Baude 13 Sep '21

13 Sep '21

You have to create a new network and it will work nicely. We couldn't make the default network work correctly in time but long-term it will work. so ... podman network create new podman run ... --network new ... On Thu, Sep 2, 2021 at 7:21 PM Till Backhaus <till(a)backha.us> wrote: > Hi, > > > > Sorry to bother you with this. I cannot reach a running container via > network using podman machine. > > I installed podman (3.3.0) via homebrew on macos (bigsur 11.5.2). > > I created a machine using > > > podman machine init > > which I then started using > > > podman machine start > > I then started a nginx container > > > podman run -p 8000:80 --rm docker://nginx > > > > I’d expect to reach the container on localhost:8000 via curl > > > curl localhost:8000 > > > curl: (7) Failed to connect to localhost port 8000: Connection refused > > But the port forwarding is configured for the machine only > > > > Inside the machine the port is forwarded: > > > podman machine ssh > > > curl localhost:8000 > > > <!DOCTYPE html> > > > … > > > > If automatic port forwarding is not possible I’d expect to be able to > reach the machine on it’s ip address. I don’t reach the machines ip (got it > from it ip addr from inside the machine) either. > > > > I didn’t find anything on this matter in the docs > https://docs.podman.io/en/latest/ . What am I missing? > > > > Thank you so much for your time! > > Best regards, > > Till > > > > (My first post here) > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io >

1 0

Podman Community Meeting Notes are now up from September 2021
by Tom Sweeney 09 Sep '21

09 Sep '21

Hey All! The meeting notes from the September 7, 2021 Podman Community Meeting are now up: https://podman.io/community/meeting/notes/2021-09-07/There's a link to the BlueJeans recording on the page if you want to see that. Best Wishes, t

1 0

Podman on macOS Update
by Tom Sweeney 08 Sep '21

08 Sep '21

Hey All, In case you're interested in the current state of affairs of Podman on macOS, with a smattering of Windows, Brent Baude gave a status update on podman.io: https://podman.io/blogs/2021/09/06/podman-on-macs.html Enjoy! t

1 0

Re: Podman machine & portforwarding
by Shion Tanaka 07 Sep '21

07 Sep '21

Till, I also hit the same problem and opened the Issue [1]. As the comment in the link says, you need to create the network beforehand. Or, adding rootless_networking = "cni" under the [containers] section of ~/.config/containers/containers.conf [1] https://github.com/containers/podman/issues/11396 ---- Shion Tanaka / Red Hat K.K. Solution Architect shtanaka(a)redhat.com 2021年9月3日(金) 9:21 Till Backhaus <till(a)backha.us>: > Hi, > > > > Sorry to bother you with this. I cannot reach a running container via > network using podman machine. > > I installed podman (3.3.0) via homebrew on macos (bigsur 11.5.2). > > I created a machine using > > > podman machine init > > which I then started using > > > podman machine start > > I then started a nginx container > > > podman run -p 8000:80 --rm docker://nginx > > > > I’d expect to reach the container on localhost:8000 via curl > > > curl localhost:8000 > > > curl: (7) Failed to connect to localhost port 8000: Connection refused > > But the port forwarding is configured for the machine only > > > > Inside the machine the port is forwarded: > > > podman machine ssh > > > curl localhost:8000 > > > <!DOCTYPE html> > > > … > > > > If automatic port forwarding is not possible I’d expect to be able to > reach the machine on it’s ip address. I don’t reach the machines ip (got it > from it ip addr from inside the machine) either. > > > > I didn’t find anything on this matter in the docs > https://docs.podman.io/en/latest/ . What am I missing? > > > > Thank you so much for your time! > > Best regards, > > Till > > > > (My first post here) > _______________________________________________ > Podman mailing list -- podman(a)lists.podman.io > To unsubscribe send an email to podman-leave(a)lists.podman.io >

2 1

Rootless - Native overlay not shown in df or mount commands
by Jorge Fábregas 07 Sep '21

07 Sep '21

Hi, Fedora 33 user here. Whenever I run a rootful container I can perform either: df -t overlay or mount -t overlay ....in the host and I can clearly see where the root filesystem of the container is actually mounted (the "merged" one). Now, with the new native overlay filesystem support for rootless containers, whenever I run a rootless one I don't see the same behavior with the mount or df commands (either as regular user or the root user). In fact, there's no overlay fs shown. I know it's there because I found them somewhere hidden in /proc/*/mounts and I also performed the "podman system reset" that Dan & Giuseppe mentioned in a recent blog post. There's got to be some explanation like perhaps it's under another "mount namespace" ...but then why do the overlay entries appear in the host when rootful containers are running? Thanks! Jorge

4 10

Coverage in CI
by Valentin Rothberg 07 Sep '21

07 Sep '21

Hi folks, We've recently been going over old work items. One of them was to collect code-coverage in CI. I gave it a shot last year and opened a PR [1] but quickly ran into the problem of uploading the thousands of coverage profiles during the end-to-end tests (i.e., test/e2e/*). They accumulated to over a dozen gigabytes. I tried trimming these down in various attempts but never managed to tame the beast. Priorities shifted and I went on to work on other things. That being said. If some of you are coverage experts in Go and want to give it a shot. Feel free to pick up the PR [1] and kick it over the finish line. As you may see, the instrumented podman binary to collect coverage has some issues related to signal handling that need to get ironed out as well. No time pressure, it's a nice-to-have. Kind regards, Valentin [1] https://github.com/containers/podman/pull/7065

1 0

Podman Community Meeting - Tuesday September 7, 2021 - 11:00 a.m. EDT (UTC-4)
by Tom Sweeney 03 Sep '21

03 Sep '21

Hi All, I'm very late getting the agenda out, but I think we've a great line up of topics for next Tuesday's Podman Community Meeting! We'll be talking about updates on the Debian/Ubuntu package, DIY Networking in rootless containers, Containerized DNS Analysis, Using Podman in an IDE, and an open forum at the end. The meeting starts at 11:00 a.m. EDT (UTC-4) on Tuesday September 7, 2021 and will be free to attend via BlueJeans (https://bluejeans.com/880216278/2568) The full agenda is here: https://podman.io/community/meeting/agenda/ For those in the US, enjoy your labor day holiday! Best wishes, t

1 0