[Podman] Re: Container health check from another container
by Александр Илюшкин
At least I tried, Valentin 😅
Yes, your interpretation is correct.
That was interesting to learn about the systemd approach.
С уважением, А. И.
вт, 21 нояб. 2023 г., 15:05 Valentin Rothberg <vrothberg(a)redhat.com>:
> On Tue, Nov 21, 2023 at 11:23 AM Александр Илюшкин <ailjushkin(a)gmail.com>
> wrote:
>
>> I apologize if I misunderstood the question. I thought about something
>> like this.
>>
>
> Thanks! I'd prefer a text explanation as I still need to interpret the
> sketch. As far as I read it, something should be blocking on the health
> state of another container.
>
> So it's not possible for one container to know the health state of another
> container. That knowledge must either be implemented in the application
> logic *inside* the container (e.g., ping a server) or be used outside the
> containers, for instance, by moving the containers into systemd units which
> will only mark the unit as ready when the health check fired.
>
>
>> вт, 21 нояб. 2023 г. в 12:49, Valentin Rothberg <vrothberg(a)redhat.com>:
>> >
>> > On Tue, Nov 21, 2023 at 10:12 AM Александр Илюшкин <
>> ailjushkin(a)gmail.com> wrote:
>> >>
>> >> For example, you can define a custom /health API for this.
>> >>
>> >> In this API you can call and process health results from another hosts
>> you are integrating with.
>> >
>> >
>> > Can you describe the use case? I don't yet fully understand what you
>> want to do. I am a bit confused as you first mentioned "another container
>> in the same pod" and now mention "another host".
>> >
>> > Kind regards,
>> > Valentin
>> >
>> >>
>> >> С уважением, А. И.
>> >>
>> >> вт, 21 нояб. 2023 г., 11:45 Михаил Иванов <ivans(a)isle.spb.ru>:
>> >>>
>> >>> Hi, is it possible to run health check on a container from another
>> container in same pod?
>> >>>
>> >>> --
>> >>>
>> >>> Michael Ivanov
>> >>>
>> >>> _______________________________________________
>> >>> 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
>>
>>
>>
>> --
>> С уважением,
>> А.И.
>>
>
1 year, 11 months
[Podman] runc start b714ab8d87af579aea314ee36964e49a807ab5025099ff3b3e140df715bf914a failed: exit status 1
by GHui Wu
I start podman as following command.
podman --log-level=debug run --rm --env-host --env-file envfile --userns=keep-id --network=host --pid=host --ipc=host --privileged -v ./Dmyjob:/Dmyjob:z -w /Dmyjob abacus:3.1.0 ./myjob.sh
But sometimes it output error "runc start xxxxx failed: exit status 1".
time="2023-02-24T14:29:21+08:00" level=error msg="remove /export/myuser/14234/podman-run-1253/runc/b714ab8d87af579aea314ee36964e49a807ab5025099ff3b3e140df715bf914a/exec.fifo: no such file or directory"
time="2023-02-24T14:29:21+08:00" level=error msg="remove /export/myuser/14234/podman-run-1253/runc/58a04ffff99f6769136a36676ff69e3631f29e8353fc155b4a211c6a496ab58d/exec.fifo: no such file or directory"
time="2023-02-24T14:29:21+08:00" level=debug msg="unable to remove container b714ab8d87af579aea314ee36964e49a807ab5025099ff3b3e140df715bf914a after failing to start and attach to it"
time="2023-02-24T14:29:21+08:00" level=debug msg="unable to remove container 58a04ffff99f6769136a36676ff69e3631f29e8353fc155b4a211c6a496ab58d after failing to start and attach to it"
time="2023-02-24T14:29:21+08:00" level=debug msg="ExitCode msg: \"`/export/home/myuser/.local/container/sbin/runc start b714ab8d87af579aea314ee36964e49a807ab5025099ff3b3e140df715bf914a` failed: exit status 1\""
time="2023-02-24T14:29:21+08:00" level=debug msg="ExitCode msg: \"`/export/home/myuser/.local/container/sbin/runc start 58a04ffff99f6769136a36676ff69e3631f29e8353fc155b4a211c6a496ab58d` failed: exit status 1\""
Error: `/export/home/myuser/.local/container/sbin/runc start 58a04ffff99f6769136a36676ff69e3631f29e8353fc155b4a211c6a496ab58d` failed: exit status 1
Error: `/export/home/myuser/.local/container/sbin/runc start b714ab8d87af579aea314ee36964e49a807ab5025099ff3b3e140df715bf914a` failed: exit status 1
2 years, 8 months
[Podman] Error: failed to connect to container's attach socket: /xxxxx/attach: no such file or directory
by GHui Wu
I start podman as following command.
podman --log-level=debug run --rm --env-host --env-file envfile --userns=keep-id
--network=host --pid=host --ipc=host --privileged -v ./Dmyjob:/Dmyjob:z -w /Dmyjob
abacus:3.1.0 ./myjob.sh
But sometimes it output error "Error: failed to connect to container's attach socket: /xxxxx/attach: no such file or directory".
time="2023-02-24T15:56:41+08:00" level=debug msg="Successfully cleaned up container ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4"
time="2023-02-24T15:56:41+08:00" level=error msg="Storage for container ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4 has been removed"
time="2023-02-24T15:56:41+08:00" level=debug msg="Removing all exec sessions for container ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4"
time="2023-02-24T15:56:41+08:00" level=debug msg="Container ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4 storage is already unmounted, skipping..."
time="2023-02-24T15:56:41+08:00" level=info msg="Storage for container ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4 already removed"
time="2023-02-24T15:56:41+08:00" level=debug msg="ExitCode msg: \"failed to connect to container's attach socket: /export/myuser/11727/1253/share/containers/storage/overlay-containers/ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4/userdata/attach: no such file or directory\""
Error: failed to connect to container's attach socket: /export/myuser/11727/1253/share/containers/storage/overlay-containers/ab2d81ec95dd0025a588ad016fb2b79db8c4e1617f0b808f756a3d25d4fca2a4/userdata/attach: no such file or directory
2 years, 8 months
[Podman] Re: podman slowly shows logs on windows
by Александр Илюшкин
> Which prompt/terminal are you using, do you see the same behavior on Windows Terminal (wt.exe), powershell.exe, and cmd?
This is not a terminal-dependent problem :( This works slow on any
terminal, and also junit testcontainers are so slow that one simple
test runs for 5 minutes because of that.
> If you do a "podman machine ssh" and then podman logs at the linux prompt, do you also see a lag?
I do see a lag using `podman machine ssh`, it freezes after each typed letter.
чт, 3 авг. 2023 г. в 17:31, Jason Greene <jason.greene(a)redhat.com>:
>
> Hi Александр,
>
> Which prompt/terminal are you using, do you see the same behavior on Windows Terminal (wt.exe), powershell.exe, and cmd?
>
> If you do a "podman machine ssh" and then podman logs at the linux prompt, do you also see a lag?
>
> Thanks!
>
>
> On Jul 27, 2023 at 3:50:29 PM, Александр Илюшкин <ailjushkin(a)gmail.com> wrote:
>>
>> I'm getting logs as quick as it produced with simple wsl prompt command)
>>
>> чт, 27 июл. 2023 г. в 17:54, Jason Greene <jason.greene(a)redhat.com>:
>>
>>
>> Sorry that should have been:
>>
>>
>> "podman --remote --url unix:///var/run/user/$(id -u)/podman/podman.sock logs <container>”
>>
>>
>>
>> On Jul 27, 2023 at 9:53:07 AM, Jason Greene <jason.greene(a)redhat.com> wrote:
>>
>> >
>>
>> > You’re welcome and thanks for the info. If, on the WSL prompt, you run:
>>
>> > "podman --remote --url /var/run/user/$(id -u)/podman/podman.sock logs <container>”
>>
>> >
>>
>> > How does the speed compare to the other two cases (direct podman command and also the windows prompt which you observed as slow)?
>>
>> >
>>
>> >
>>
>> > On Jul 27, 2023 at 9:17:19 AM, Александр Илюшкин <ailjushkin(a)gmail.com> wrote:
>>
>> >>
>>
>> >> Jason, hi, thank you for your feedback. Yes, exactly, using the WSL
>>
>> >> prompt all commands work fast.
>>
>> >>
>>
>> >> чт, 27 июл. 2023 г. в 17:13, Jason Greene <jason.greene(a)redhat.com>:
>>
>> >>
>>
>> >>
>>
>> >> Hey Александр,
>>
>> >>
>>
>> >>
>>
>> >> Do you see a difference when you run this on the WSL prompt? If you do "wsl -d podman-machine-default”, then podman logs <container>?
>>
>> >>
>>
>> >>
>>
>> >>
>>
>> >> On Jul 21, 2023 at 2:19:01 PM, Daniel Walsh <dwalsh(a)redhat.com> wrote:
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > 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, 3 months
[Podman] Re: podman slowly shows logs on windows
by Jason Greene
Sorry that should have been:
"podman --remote --url unix:///var/run/user/$(id -u)/podman/podman.sock
logs <container>”
On Jul 27, 2023 at 9:53:07 AM, Jason Greene <jason.greene(a)redhat.com> wrote:
> You’re welcome and thanks for the info. If, on the WSL prompt, you run:
> "podman --remote --url /var/run/user/$(id -u)/podman/podman.sock logs
> <container>”
>
> How does the speed compare to the other two cases (direct podman command
> and also the windows prompt which you observed as slow)?
>
>
> On Jul 27, 2023 at 9:17:19 AM, Александр Илюшкин <ailjushkin(a)gmail.com>
> wrote:
>
>> Jason, hi, thank you for your feedback. Yes, exactly, using the WSL
>> prompt all commands work fast.
>>
>> чт, 27 июл. 2023 г. в 17:13, Jason Greene <jason.greene(a)redhat.com>:
>>
>>
>> Hey Александр,
>>
>>
>> Do you see a difference when you run this on the WSL prompt? If you do
>> "wsl -d podman-machine-default”, then podman logs <container>?
>>
>>
>>
>> On Jul 21, 2023 at 2:19:01 PM, Daniel Walsh <dwalsh(a)redhat.com> wrote:
>>
>> >
>>
>> > 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, 3 months
[Podman] Re: Container health check from another container
by Valentin Rothberg
On Tue, Nov 21, 2023 at 11:23 AM Александр Илюшкин <ailjushkin(a)gmail.com>
wrote:
> I apologize if I misunderstood the question. I thought about something
> like this.
>
Thanks! I'd prefer a text explanation as I still need to interpret the
sketch. As far as I read it, something should be blocking on the health
state of another container.
So it's not possible for one container to know the health state of another
container. That knowledge must either be implemented in the application
logic *inside* the container (e.g., ping a server) or be used outside the
containers, for instance, by moving the containers into systemd units which
will only mark the unit as ready when the health check fired.
> вт, 21 нояб. 2023 г. в 12:49, Valentin Rothberg <vrothberg(a)redhat.com>:
> >
> > On Tue, Nov 21, 2023 at 10:12 AM Александр Илюшкин <ailjushkin(a)gmail.com>
> wrote:
> >>
> >> For example, you can define a custom /health API for this.
> >>
> >> In this API you can call and process health results from another hosts
> you are integrating with.
> >
> >
> > Can you describe the use case? I don't yet fully understand what you
> want to do. I am a bit confused as you first mentioned "another container
> in the same pod" and now mention "another host".
> >
> > Kind regards,
> > Valentin
> >
> >>
> >> С уважением, А. И.
> >>
> >> вт, 21 нояб. 2023 г., 11:45 Михаил Иванов <ivans(a)isle.spb.ru>:
> >>>
> >>> Hi, is it possible to run health check on a container from another
> container in same pod?
> >>>
> >>> --
> >>>
> >>> Michael Ivanov
> >>>
> >>> _______________________________________________
> >>> 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
>
>
>
> --
> С уважением,
> А.И.
>
1 year, 11 months
[Podman] Re: Podman Community Meeting - Tues October 3, 2023, 11:00 am EDT (UTC-4)
by Valentin Rothberg
On Thu, Oct 5, 2023 at 7:40 AM Dewayne Branch <bdbranch(a)gmail.com> wrote:
> FYI
>
> https://www.phoronix.com/news/Linux-Foudation-OpenPubkey
>
> What is our response?
>
Thanks for sharing!
There is sigstore [1] which is already under the Linux Foundation.
sigstore signing is supported by Podman, cosign and other tools.
I do not yet understand why Docker is going a separate path but am curious
to see what will happen.
[1]
https://www.linuxfoundation.org/blog/blog/adopting-sigstore-incrementally
> On Thu, Sep 28, 2023, 5:35 PM Tom Sweeney <tom.sweeney(a)redhat.com> wrote:
>
>> Hi All!
>> The next Podman Community Meeting is happening in just over 5 days from
>> now, on next Tuesday Oct 3, 2023, at 11:00am EDT(UTC-4). We'll have a demo
>> on Quadlet, one on Modules, and room for more if you have topics. Agenda
>> with Conference link: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w
>>
>> Hope to see you there!
>>
>> t
>>
>> _______________________________________________
>> 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
[Podman] Re: Container health check from another container
by Александр Илюшкин
I apologize if I misunderstood the question. I thought about something
like this.
вт, 21 нояб. 2023 г. в 12:49, Valentin Rothberg <vrothberg(a)redhat.com>:
>
> On Tue, Nov 21, 2023 at 10:12 AM Александр Илюшкин <ailjushkin(a)gmail.com> wrote:
>>
>> For example, you can define a custom /health API for this.
>>
>> In this API you can call and process health results from another hosts you are integrating with.
>
>
> Can you describe the use case? I don't yet fully understand what you want to do. I am a bit confused as you first mentioned "another container in the same pod" and now mention "another host".
>
> Kind regards,
> Valentin
>
>>
>> С уважением, А. И.
>>
>> вт, 21 нояб. 2023 г., 11:45 Михаил Иванов <ivans(a)isle.spb.ru>:
>>>
>>> Hi, is it possible to run health check on a container from another container in same pod?
>>>
>>> --
>>>
>>> Michael Ivanov
>>>
>>> _______________________________________________
>>> 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
--
С уважением,
А.И.
1 year, 11 months
[Podman] Re: podman slowly shows logs on windows
by Александр Илюшкин
Unfortunately it seems that there are no limits on resources :-(
```
"Resources": {
"CPUs": 12,
"DiskSize": 5989466112,
"Memory": 3045093376
},
```
```
C:\Users\Alexander.Iljushkin> podman machine inspect
[
{
"ConfigPath": {
"Path":
"C:\\Users\\Alexander.Iljushkin\\.config\\containers\\podman\\machine\\wsl\\podman-machine-default.json"
},
"ConnectionInfo": {
"PodmanSocket": null,
"PodmanPipe": {
"Path": "\\\\.\\pipe\\podman-machine-default"
}
},
"Created": "2023-07-19T14:24:31.6499354+03:00",
"Image": {
"IgnitionFilePath": {
"Path": ""
},
"ImageStream": "35",
"ImagePath": {
"Path":
"C:\\Users\\Alexander.Iljushkin\\.local\\share\\containers\\podman\\machine\\wsl\\podman-machine-default_fedora-podman-amd64-v37.0.50.tar"
}
},
"LastUp": "2023-07-27T16:59:52.9665852+03:00",
"Name": "podman-machine-default",
"Resources": {
"CPUs": 12,
"DiskSize": 5989466112,
"Memory": 3045093376
},
"SSHConfig": {
"IdentityPath":
"C:\\Users\\Alexander.Iljushkin\\.ssh\\podman-machine-default",
"Port": 58713,
"RemoteUsername": "user"
},
"State": "running"
}
]
```
ср, 26 июл. 2023 г. в 19:06, Александр Илюшкин <ailjushkin(a)gmail.com>:
>
> 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, 3 months
[Podman] Podman Community Cabal Meeting, Thu April 20, 2023, 11:00 a.m. EDT (UTC-5)
by Tom Sweeney
Hi All,
The Podman Community Cabal meeting is happening two weeks from right
now, on Thur, April 20, 2023 at 11:00am EDT (UTC-5). Currently, our
agenda is wide open for topics, so if you have a topic to discuss about
Podman, please add it to the agenda!
https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both
Thanks!
t
2 years, 7 months
