- Podman - Podman List Archives

podman systemd file for mssql-server
by mwindham＠troglobytor.com 24 Jan '23

24 Jan '23

I did another generate today and after some tinkering with options got the below, and I don't have a clue what went wrong in original post. sudo podman generate systemd -n -f --restart-policy=always sqlx22 >pdm2sysd.txtsudo cp container-sqlx22.service /etc/systemd/system sudo systemctl enable container-sqlx22.service works # container-sqlx22.service # autogenerated by Podman 4.2.0 # Tue Jan 24 17:00:30 CST 2023 [Unit] Description=Podman container-sqlx22.service Documentation=man:podman-generate-systemd(1) Wants=network-online.target After=network-online.target RequiresMountsFor=/run/containers/storage [Service] Environment=PODMAN_SYSTEMD_UNIT=%n Restart=always TimeoutStopSec=70 ExecStart=/usr/bin/podman start sqlx22 ExecStop=/usr/bin/podman stop -t 10 sqlx22 ExecStopPost=/usr/bin/podman stop -t 10 sqlx22 PIDFile=/run/containers/storage/overlay-containers/afcbd216eedb0d74075a522e8 fc6cfc5a8dc8a0a3dfb2ce65434891b30fb0eb8/userdata/conmon.pid Type=forking [Install] WantedBy=default.target

1 0

podman systemd file for mssql-server
by mwindham＠troglobytor.com 24 Jan '23

24 Jan '23

I used "podman generate systemd" for a configured sqlx22 named container and got the attached file which seems to have all the initial configuration command. What would be the minimal revised ExecStart to use after configuration? Do I need to keep specifying name and hostname? I would think all the -e 's should be omitted? When I start from command line all I use is "sudo podman start sqlx22". podman generated ExecStart: ExecStart=/usr/bin/podman run \ --cidfile=%t/%n.ctr-id \ --cgroups=no-conmon \ --rm \ --sdnotify=conmon \ --replace \ -e ACCEPT_EULA=Y \ -e MSSQL_SA_PASSWORD=SQueeZY2*ZX \ -e MSSQL_PID=Express \ --name sqlx22 \ --hostname sqlx22 \ -p 1433:1433 \ -d mcr.microsoft.com/mssql/rhel/server:2022-latest

1 0

Container restart issue: Failed to attach 1 to compat systemd cgroup
by Lewis Gaul 19 Jan '23

19 Jan '23

Hi Podman team, I came across an unexpected systemd warning when running inside a container - I emailed systemd-devel (this email summarises the thread, which you can find at https://lists.freedesktop.org/archives/systemd-devel/2023-January/048723.ht…) and Lennart suggested emailing here. Any thoughts would be great! There are two different warnings seen in different scenarios, both cgroups related, and I believe related to each other given they both satisfy the points below. The first warning is seen after 'podman restart $CTR', coming from https://github.com/systemd/systemd/blob/v245/src/shared/cgroup-setup.c#L279: Failed to attach 1 to compat systemd cgroup /machine.slice/libpod-5e4ab2a36681c092f4ef937cf03b25a8d3d7b2fa530559bf4dac4079c84d0313.scope/init.scope: No such file or directory The second warning is seen on every boot when using '--cgroupns=private', coming from https://github.com/systemd/systemd/blob/v245/src/core/cgroup.c#L2967: Couldn't move remaining userspace processes, ignoring: Input/output error Failed to create compat systemd cgroup /system.slice: No such file or directory ... Both warnings are seen together when restarting a container using private cgroup namespace. To summarise: - The warnings are seen when running the container on a Centos 8 host, but not on an Ubuntu 20.04 host - It is assumed this issue is specific to cgroups v1, based on the warning messages - Disabling SELinux on the host with 'setenforce 0' makes no difference - Seen with systemd v245 but not with v230 - Seen with '--privileged' and in non-privileged with '--cap-add sys_admin' - Changing the cgroup driver/manager doesn't seem to have any effect - The same is seen with docker except when running privileged the first warning becomes a fatal error after hitting "Failed to open pin file: No such file or directory" (coming from https://github.com/systemd/systemd/blob/v245/src/core/cgroup.c#L2972) and the container exits (however docker doesn't claim to support systemd) Some extra details copied from the systemd email thread: - On first boot PID 1 can be found in /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/init.scope/cgroup.procs, whereas when the container restarts the 'init.scope/' directory does not exist and PID 1 is instead found in the parent (container root) cgroup /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/cgroup.procs (also reflected by /proc/1/cgroup). This is strange because systemd must be the one to create this cgroup dir in the initial boot, so I'm not sure why it wouldn't on subsequent boot. - I confirmed that the container has permissions to create the dir by executing a 'mkdir' in /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/ inside the container after the restart, so I have no idea why systemd is not creating the 'init.scope/' dir. I notice that inside the container's systemd cgroup mount 'system.slice/' does exist, but 'user.slice/' also does not (both exist on normal boot). This should be reproducible using the following: cat << EOF > Dockerfile FROM ubuntu:20.04 RUN apt-get update -y && apt-get install systemd -y && ln -s /lib/systemd/systemd /sbin/init ENTRYPOINT ["/sbin/init"] EOF podman build . --tag ubuntu-systemd podman run -it --name ubuntu --privileged --cgroupns private ubuntu-systemd podman restart ubuntu Thanks, Lewis

2 1

Podman Community Cabal Meeting - Thursday January 19, 2023, 11:00 a.m. EST (UTC-5)
by Tom Sweeney 18 Jan '23

18 Jan '23

Hi All, The next Podman Community Cabal meeting is happening in just under 20 hours from now, at 11:00am EST (UTC-5). We'll be talking about Podman v4.4, auto-closing issues, and more! Agenda with video conference link: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both <https://t.co/sYgIaGn8rS> Hope to see you there! t

1 0

bolt_state.db: no such file or directory
by GHui Wu 18 Jan '23

18 Jan '23

I run "podman run --rm xxxx". When the container runs completely, there output the following error. Could not retrieve exit code: error opening database /tmp/3199/19531/share/containers/storage/libpod/bolt_state.db: open /tmp/3199/19531/share/containers/storage/libpod/bolt_state.db: no such file or directory I have checked the /tmp/3199/19531/share/containers/storage, there is no such directory.

1 0

Container Plumbing Days Conference - 2023
by Tom Sweeney 17 Jan '23

17 Jan '23

Hi All, The Container Plumbing Days conference will be held virtually on March 22 and 23, 2023, from around 1300 UTC to 1800 UTC daily. There will be no charge for the conference, and all are welcome. We are still looking for presenters for the conference. If you have a container-related topic you'd like to run a session for, we'd love to get you on the schedule! However, the deadline for topic submissions is fast approaching. Topic submissions are due by Monday, January 23, 2023 at 23:59 UTC (7:00 p.m. Eastern). Please go here: https://twitter.com/Podman_io/status/1613904237066428416 to propose a session. More information, including registration information on the Container Plumbing Days conference, can be found here: https://containerplumbing.org Hope to see you there! t

1 0

=?utf-8?q?=5BPodman=5D?=(Meta) Security warnings for podman mailing list
by Joost Molenaar 12 Jan '23

12 Jan '23

Hi all, for ~every message posted to this list, some email clients display an error, in my case "This email has failed its domain's authentication requirements. It may be spoofed or improperly forwarded." These are the authentication results for a recent message from the list: Authentication-Results: mailin008.protonmail.ch; arc=none smtp.remote-ip=8.43.85.227 Authentication-Results: mailin008.protonmail.ch; dkim=none Authentication-Results: mailin008.protonmail.ch; spf=none smtp.mailfrom=lists.podman.io Authentication-Results: mailin008.protonmail.ch; dmarc=fail (p=none dis=none) header.from=redhat.com If I understand correctly, Mailman has an option[1] to change the From: header in the email and add the original sender's name and address to the Reply-To: header, which leads to a slightly worse user experience, but is better for security because it reduces the number of false positives we get exposed to. So my question is, could we enable DMARC mitigation to reduce warning fatigue? Regards, Joost Molenaar [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…

4 4

Deprecation announcement for CNI plugins
by Brent Baude 10 Jan '23

10 Jan '23

Folks, I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself: https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/

5 6

Thursday December 15, 2022 Podman Community Cabal Meeting Canceled!
by Tom Sweeney 12 Dec '22

12 Dec '22

Hi All, As we have not subjects as of yet, and I have had a number of people tell me they won't be able to attend due to their holidays starting early or other related holiday gatherings going on, I'm going to cancel the Podman Community Cabal Meeting for Thursday December 15, 2022 at 11:00 a.m. EST (UTC-5). The next Podman Community Cabal Meeting will be held on Thursday January 19, 2023 at 11:00 a.m. EST (UTC-5). The next Podman Community Meeting will be held on Tuesday February 7, 2023 at 11:00 a.m. EST (UTC-5). As a reminder, the Cabal meetings are generally to talk about Design questions, futures, and related items in regards to Podman. The Community meeting is used for announcements, demos, and things of interest not only for Podman, but anything container related. If you have something that you'd like to present at either meeting please let me know. Likewise, if you have seen something interesting in the container world that you'd like to hear more about, please let me know and I'll see if I can find someone to do a presentation on it. I hope you and your families have a very safe and happy holiday season. Happy New Year to you All! Best Wishes, t

1 0

kratom.org - Reliable Kratom Resources About Kratom
by redddorsey1014＠outlook.com 09 Dec '22

09 Dec '22

Founded in 2014, kratom.org (kratom.org) is an advocacy group that is dedicated to protecting the rights of consumers. Specifically, the organization aims to educate lawmakers, customers, vendors and growers about the benefits of kratom. kratom.org has its own website, which features information on the science behind kratom. It also provides links to scientific studies and infographics. The website includes a pre-written letter that you can send to your congressperson. There is also a newsletter that you can subscribe to on kratom.org's site. You can also donate using PayPal, wire transfer or by check. kratom.org has been fighting against kratom bans in various parts of the country since it was founded, and the organization is attempting to win over some members of Congress. kratom.org is run by a board of directors that consists of several government members and scientists. These individuals are responsible for ensuring that kratom.org complies with state and federal regulations. They are also responsible for ensuring that kratom.org remains compliant with the IRS. kratom.org is also a not-for-profit organization that is tax-exempt. The organization is made up of a group of dedicated consumers, scientists, and lawmakers. The organization is dedicated to educating the public about kratom, and believes that education is the best way to change attitudes about kratom. It is also responsible for ensuring that consumers have access to safe and legal kratom products. The organization is also dedicated to combating misinformation about kratom. kratom.org's mission is to protect consumers from unjustified bans and regulatory actions. The organization strives to increase consumer confidence in kratom, which is often lost in the political shuffle. It also wants to be a model for other countries to follow. It hopes to change the perceptions of the United States regarding kratom. It believes that consumers are often overlooked in the U.S. and that it is time that they were given their fair share of attention. kratom.org believes that education is the best way to change the minds of the consumer, the law makers and the regulators. It also believes that educating consumers about kratom can help change attitudes about growers, vendors and manufacturers. The organization's website provides consumers with the science behind kratom, a list of current news and events about kratom, and a way to contact their congressional representatives. kratom.org is made up of people who are dedicated to ensuring that consumers have access to kratom. It is a non-profit organization that depends on donations to fund its operations. The organization has been fighting against kratom bans and regulatory actions in various parts of the country since it was created. Its website features a list of current news and events about the plant, a way to contact your congressional representatives, and a newsletter that you can subscribe to. kratom.org has been fighting against the FDA's inaccurate characterization of kratom. It also wants to help the FDA change course. Website: https://kratom.org/

1 0