[Podman] Thursday December 15, 2022 Podman Community Cabal Meeting Canceled!
by Tom Sweeney
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
2 years, 9 months
[Podman] Re: passt (pasta(1)) package to be included in Fedora CoreOS 37/38
by Daniel Walsh
On 3/9/23 03:31, Mehdi Haghgoo via Podman wrote:
> That's great to hear.
>
Currently podman on Windows/WSL does NOT use coreos. It does use
Fedora. We would need to make sure that pasta is included in the image
that is used for WSL.
Jason could you look into this. I think we should think about changing
the default from slirp4netns to pasta by default in Fedora, which would
fix this issue for all users
> Thanks Stefano
>
> On Thu, Mar 9, 2023 at 14:36, Stefano Brivio
> <sbrivio(a)redhat.com> wrote:
> On Wed, 8 Mar 2023 22:17:38 +0000 (UTC)
> Mehdi Haghgoo <powergame_coder2(a)yahoo.com> wrote:
> That's great
> > I mean Podman Desktop, which apparently downloads and initializes a
> > coreos instance on startup. So, is passt supported with Podman
> > Desktop on win& mac?
>
> I never used it on Windows, but yes, my understanding is that it
> should
> work there -- it simply runs Fedora CoreOS in a virtualised
> environment.
>
> --
> Stefano
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
2 years, 6 months
[Podman] Re: exec - shell functions ?
by lejeczek
On 19/06/2023 07:55, Valentin Rothberg wrote:
> On Sun, Jun 18, 2023 at 10:59 AM lejeczek via Podman
> <podman(a)lists.podman.io> wrote:
>
> Hi guys.
>
> How do you 'exec' your container shell functions
> without going into shell interactively?
>
>
> You can run, for instance, `podman exec $container -s
> "$functions"`.
>
I was looking at a few websites which suggest docker exec
this way:
-> $ docker exec 123456789abc bash -c "{command 1} ;
{command 2}"
which does not work, but this does, with/in podman:
-> $ podman container exec freeipa.mine.priv bash -c "source
/root/.bashrc; __ipaCollectBits"
thanks, L.
2 years, 2 months
[Podman] Rootless container startup failure at bootup, launches fine manually
by jklaiho＠iki.fi
We've got a Ubuntu 22.04 server running a rootless container as a systemd user service on Podman 4.4.2, using Quadlet. Podman and its dependencies are installed from binary releases on GitHub and/or from source.
Last night the server required a reboot due to some security updates, but the service/container failed to come back up after the boot. In the morning, I was able to manually start it up with `systemctl --user start cms_backend` with no changes to any configuration in the meantime.
Here's the full journalctl output for this unit from last night after the reboot (timestamps removed for brevity):
systemd[746]: cms_backend.service: unit configures an IP firewall, but not running as root.
systemd[746]: (This warning is only shown for the first unit using IP firewalling.)
systemd[746]: Starting CMS Backend...
cms_backend[787]: time="2023-05-25T03:01:58+03:00" level=error msg="Refreshing container 8f03c9c90e6f8aab02344284ba760fe8ddbf52becb7ba95c383fb80c3bd04405: retrieving temporary directory for container 8f03c9c90e6f8aab02344284ba760fe8ddbf52becb7ba95c383fb80c3bd04405: no such container"
podman[787]: 2023-05-25 03:01:59.000295722 +0300 EEST m=+0.107418901 system refresh
cms_backend[787]: time="2023-05-25T03:01:59+03:00" level=warning msg="Found incomplete layer \"b767c3f7da27350a451d15f1e972cdd874ea0e6f4c38fad1f644686f0831786f\", deleting it"
cms_backend[787]: time="2023-05-25T03:01:59+03:00" level=error msg="Free container lock: no such file or directory"
podman[787]: 2023-05-25 03:01:59.037410032 +0300 EEST m=+0.144533221 container remove 8f03c9c90e6f8aab02344284ba760fe8ddbf52becb7ba95c383fb80c3bd04405 (image=<redacted>:latest, name=cms_backend, com.<redacted>.cms.commit_sha=99d36804, com.<redacted>.cms.component=server, com.<redacted>.cms.pipeline_id=25445, PODMAN_SYSTEMD_UNIT=cms_backend.service)
cms_backend[787]: Error: remove /run/user/1001/cms_backend.cid: no such file or directory
podman[787]: 2023-05-25 03:01:59.00150107 +0300 EEST m=+0.108624239 image pull <redacted>:latest
systemd[746]: cms_backend.service: Main process exited, code=exited, status=125/n/a
systemd[746]: cms_backend.service: Failed with result 'exit-code'.
systemd[746]: Failed to start CMS Backend.
Here's the Quadlet generator we use:
[Unit]
Description=CMS Backend
Wants=network-online.target
After=network-online.target
[Container]
Image=<redacted>:latest
ContainerName=cms_backend
Exec=/bin/bash -c "pip install -q -e . \
&& python project/manage.py migrate -v 1 \
&& python project/manage.py tailwind install \
&& python project/manage.py tailwind build \
&& python project/manage.py collectstatic --noinput \
&& python -Wd project/manage.py check \
&& exec gunicorn --workers 8 --threads 4 --worker-class gthread --worker-tmp-dir /dev/shm --error-logfile - --bind 0.0.0.0:8000 --pythonpath project cms_site.wsgi:application
EnvironmentFile=/home/cms/.cms_backend.env
RemapUsers=manual
RemapUid=0:0:1
RemapUid=100:1:1
RemapGid=0:0:1
RemapGid=65534:1:1
Network=pasta:-t,auto,-T,auto
# TODO change to native format after Podman 4.5 upgrade
PodmanArgs=--log-driver=journald \
--mount type=bind,source=/var/log/cms,target=/logs \
--mount type=bind,source=/srv/cms/staticfiles,target=/staticfiles
[Install]
WantedBy=default.target
- - - - -
The container itself is a lightly customized official Python 3.11 image running a Django application, practically identical to others that we're running with no similar issues. The entry point of the image is ["/usr/bin/dumb-init", "--"]. Like I said, the service came up manually just fine several hours after the initial failure, so it doesn't seem likely that this is a problem in our application code.
I can't decipher the error messages, can someone?
2 years, 3 months
[Podman] Re: podman slowly shows logs on windows
by Александр Илюшкин
Guys, I think I know why the logs command is slow, I also started to
use postgresql in podman and I noticed that queries are also slow in
comparison to docker.
I think I might change memory and CPU usage default preferences and
check if that was the case. Could you please point me in the right
direction?
вс, 23 июл. 2023 г. в 23:52, Александр Илюшкин <ailjushkin(a)gmail.com>:
>
> Slow means I am getting this batched output at the speed of one screen
> in 0.5 - 1 second.
> It means that docker image has already ended with exit code 0 but its
> logs are still updating like it is still working.
>
> пт, 21 июл. 2023 г. в 22:19, Daniel Walsh <dwalsh(a)redhat.com>:
> >
> > On 7/21/23 02:54, Александр Илюшкин wrote:
> > > Hey guys, I've switched from docker to podman and I noticed that command
> > >
> > > podman logs <container name> works extremely slow
> > >
> > > What should be done to fix this?
> > >
> > I guess we would need to know what extremely slow means.
> >
> > Jason, any ideas?
> > _______________________________________________
> > Podman mailing list -- podman(a)lists.podman.io
> > To unsubscribe send an email to podman-leave(a)lists.podman.io
>
>
>
> --
> С уважением,
> А.И.
--
С уважением,
А.И.
2 years, 1 month
[Podman] Re: Podman for Android
by Paul Holzinger
Hi,
see https://github.com/containers/podman/discussions/17717
The biggest problem seems to be the kernel that is shipped in android.
Paul
On Thu, May 4, 2023 at 8:46 AM Valentin Rothberg <vrothberg(a)redhat.com>
wrote:
> Hi Mehdi,
>
> There are no official Podman binaries or packages provided by upstream for
> Android. But as you've mentioned: Android is based on Linux, so it should
> be technically possible to run Podman there.
>
> Happy hacking and kind regards,
> Valentin
>
> On Thu, May 4, 2023 at 12:45 AM Mehdi Haghgoo via Podman <
> podman(a)lists.podman.io> wrote:
>
>> Hey all,
>>
>> I have recently been interested in running as much of my software tools
>> on Android as possible. I already find lots of packages installable on
>> Termux app (via its package manager "pkg").
>>
>> Being able to run containerized apps seems very tempting to me.
>> I wonder if Podman has Arm binaries for Android. Is it possible for
>> Podman to run on Android? Android is Linux after all, and Podman can run
>> rootless. Am I missing something here?
>>
>> M
>> _______________________________________________
>> Podman mailing list -- podman(a)lists.podman.io
>> To unsubscribe send an email to podman-leave(a)lists.podman.io
>>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
2 years, 4 months
[Podman] Re: Will there be a Podman extension for VS Code?
by Daniel Walsh
On 2/5/23 10:13, Mehdi Haghgoo via Podman wrote:
> Brent that would be great.
>
> By the way, does Docker Desktop for Windows use a mechanism different
> from that of Podman to provide container experience?
>
> If they work similiarly, maybe there are workarounds to make current
> Docker extension work with Podman as well on Windows.
>
I believe that is what most people do. But we heard of a recent issue in
the latest version of vscode that broke compatibility. Basically podman
and docker command have slightly different output in some of the CLI
calls, which is causing breakage. We were informed that upstream VS Code
was working to handle the difference.
> On Sunday, February 5, 2023 at 07:31:52 PM GMT+3:30, Brent Baude
> <bbaude(a)redhat.com> wrote:
>
>
> I believe so. It is being worked on as we speak.
>
> On Sun, Feb 5, 2023 at 8:53 AM Mehdi Haghgoo via Podman
> <podman(a)lists.podman.io> wrote:
>
> Hi,
>
> Will there ever be a Docker-Desktop-compatible Podman extension
> for VS Code?
>
> I think it is very much needed, especially on Windows.
>
>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
2 years, 7 months
