Upgrade Recommendations from 1.4.2 to 3.3.1
by Christopher.Miller＠gd-ms.com
Hello, currently running Podman 1.4.2 on RHEL 8.1 and want to upgrade 3.3.1 so we can take advantage of the newer features (like networking).
I am running containers currently in the 1.4.2 environment. Is there anything to think of or do before doing an upgrade, or a best practice?
Thanks
Chris Miller
Altron INC.
703-814-7647
Christopher.miller(a)altroninc.com
Christopher.Miller(a)gd-ms.com<mailto:Christopher.Miller@gd-ms.com>
2 years, 9 months
localhost no more - ?
by lejeczek
Hi guys.
If I remember correctly both root full & less containers could talk(cni
net) to localhost which was the host itself - was the removed recently
or my memory fails me and that never worked? (if so then why?)
many thanks, L
2 years, 9 months
=?utf-8?q?=5BPodman=5D?=(Un)subscription is broken
by Konstantin Kharlamov
When I subscribed to this list, it took multiple days before I got confirmation. By the moment when I gotten it I no longer needed the mailing list.
On top of that, now that I'm trying to unsubscribe, sending a mail to podman-leave(a)lists.podman.io does nothing at all. Over last 3-4 days I send like a dozen of them, it does absolutely nothing.
2 years, 9 months
Podman 4.0rc4 and network packages
by Brent Baude
Today, we have cut a Podman 4.0rc4 release upstream. We would love for
people to begin testing this with their usual Podman usage. Moreover, as
has been shared at length over the last six months, Podman 4 will default
to a new network stack developed by our team. This is something we really
would like people to test as networking has always been problematic for
Podman.
I have posted a set of brief instructions for testing Podman 4 with its
network stack. Please consult
https://podman.io/blogs/2022/02/04/network-usage.html for those
instructions.
As usual, we would love your feedback. Please submit a github issue should
you find any problems -> https://github.com/containers/podman/issues
We are likely less than three weeks away from its final 4.0 release. Any
help the community can provide now will benefit the release and users of
Podman 4.
Brent
2 years, 9 months
How do you add directory listing to the php:7.2-apache image?
by Jeroen Verhoeckx
Hello Podman developers,
I signed up for this mailing list for a different question, but because I already solved that one, I will ask another.
It’s not really related to Podman but to a specific container image. Hopefully you don't mind for one time.
Question:
Does somebody know how I can add directory listing to the [php:7.2-apache](https://hub.docker.com/_/php/) image?
When I look inside the container it should be enabled (see code below) but when I add directories and files to the mounted volume (see command below) the directories and files aren't shown?
Content of the file /etc/apache2/apache2.conf :
<Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
I use the following command to run the image:
podman run --rm --detach -p 8080:80 --name webserver -v ~/Webserver:/var/www/html:Z php:7.2-apache
I don't know why the code Options Indexes doesn't work as expected. Does somebody has an idea?
Your sincerely,
Jeroen Verhoeckx
--------------------------------------------------------
Support the independent web, use [Firefox](https://www.mozilla.org/en-US/firefox/new/)
2 years, 9 months
podman volume performance
by Michael Ivanov
Greetings,
I am running oracle using podman volume for data (it is not for production,
of course, development only). So far I did not notice anything noticeably
wrong about it, but today I observed, that adump directory has a lot of files
and decided to clean it up (just rm -rf adump). As of time of writhing the
command runs for about half an hour and did not yet complete. Ten minutes
ago I checked number of remaining files and it was about 350000. The removal
goes at a rate on about 1000 files per minute or so. On hosting system
fuse-overlayfs process takes 99% cpu.
My system is rocky linux (former centos) 8.5. I installed podman from standard
rocky linux repo, no external repos were used. Podman version is3.2.3, crun 0.20.1
is used fpr container runtime. Underlying fs for container storage is ext4.
I did not do any special setup/configuration at all, apart from creating an lvm
for co=ntainer storage and mounting it under /home/xxxx/.local/share/containers
(podman runs rootless).
Is this behaviour normal?
Best regards,
--
\ / | |
(OvO) | Михаил Иванов |
(^^^) | |
\^/ | E-mail: ivans(a)isle.spb.ru |
^ ^ | |
2 years, 9 months
journald log driver not working
by Ranbir
Hello Everyone,
I'm testing out using journald for logging from one of my containers. I
think I configured it correctly, but I don't see anything in the path I
passed to it.
Here's the create command I used:
CreateCommand": [
"podman",
"run",
"-d",
"--name",
"postgrey",
"--pod",
"mailman",
"--volume",
"postgrey:/var/spool/postfix/postgrey:Z",
"--log-driver",
"journald",
"--log-opt",
"path=/var/log/containers/postgrey.log",
"postgrey"
],
/var/log/containers is empty:
# ls -l /var/log/containers/
total 0
Docker's docs on retrieving the logs with journalctl don't show me
anything:
journalctl CONTAINER_NAME=postgrey
-- Logs begin at Wed 2022-01-19 17:04:20 EST, end at Tue 2022-01-25
18:40:27 EST. --
-- No entries --
Incidentally, I used podman to crate the systemd unit files for the pod
and dumped them into /etc/systemd/system. I'm starting, stopping, etc
the pod using systemctl.
Using journald for logging means the container's logs get written to
the host's journal, right? If that's true, what am I doing wrong?
--
Ranbir
2 years, 9 months
cannot assign requested address
by lejeczek
Hi guys,
does anybody see this, for rootless containers?
-> $ podman container logs -f nextcloud.in.ccn
Error: initial journal cursor: failed to get cursor: cannot assign
requested address
container is created with:
-> $ podman run -d --network podman --restart=always --privileged
--security-opt label=disable....
Also, I do not see 'podman' instantiate its default cni network.
It's on centOS 8 with 3.4.1-dev
many thanks, L.
2 years, 9 months
Why it is impossible to run some containers on some platforms?
by Pavel Sosin
Dear colleagues, please, compare CRun and runc implementation. CRun lacks
some dependencies like seccomp,etc. Most RedHat UBI, ... images were cut
from the distro together with systemd2, logind, resourced, oomd, ...
Running bash in the systems with user's sessions managed by systemd2
requires 1. Communication with systemd on the host to put the container
cgroup into the right place. 2. Starting the user's session inside the
container. You can see it clearly if you pull/from/unshare/mount ubi or
fedora image using buildah.
/bin/bash in the userspace ,I suppose can run correctly only inside user's
session and borrows session's resources. What about annotating "systemd"
images and initializing them using systemd by the default?
2 years, 9 months
