5:35 a.m.
I really appreciate the help, guys. So I asked my pals from the security
department to turn off my anti-virus scanning software and it didn't help a
bit. I started a new podman machine, and the `podman machine ssh` is still
freezing.
My Windows version is
[image: image.png]
`wsl —update` shows me Critical error, I think that this might be connected
with turned off windows update, because pals from the support department
control all updates by their own rules.
`wsl --version` shows me a help page :(
So I will try to ask our tech department for future updates.
С уважением, А. И.
пт, 4 авг. 2023 г., 19:43 Jason Greene <jason.greene(a)redhat.com>:
On Aug 4, 2023 at 2:58:11 AM, Александр Илюшкин
<ailjushkin(a)gmail.com>
wrote:
> 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.
>
Ok thanks for ruling out a terminal/pty problem.
> 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.
>
Are you running any Firewall/Anti-Virus software that might be
intercepting networking connections for scanning purposes? If so can you
try temporarily disabling it and seeing if the problem goes away.
If not it could also be there is a WSL bug (either with networking, or
could be something more exotic like the hv virt RNG is slowing crypto if
the problem is only affecting ssh traffic). Can you try ensuring you are on
a later generation WSL?
If you run wsl —version, you should get something like 1.2.5.0. If instead
you get help text, you are running the older generation. To update:
1. Double check you are running 21H1, 21H2, or 22H2 (this can be seen
using the winver command), if not you need to keep running windows update
until it suggests applying 22H2 and then accept that.
2. Make sure you have applied all current updates on top of 22H2 (run
update again after rebooting)
3. Run wsl —update, which should pull down the store version
4. Double check wsl —version is now displaying versions
> чт, 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
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >> --
>
> >
>
> > >> С уважением,
>
> >
>
> > >> А.И.
>
> >
>
> > >>
>
> >
>
> >
>
> >
>
> > --
>
> > С уважением,
>
> > А.И.
>
> >
>
>
>
> --
> С уважением,
> А.И.
>
>
