I don't know how to move forward: dropped packets for localhost web server hosted on rootless container on AMD Macs, not observed on WSL Windows. #14275
Unanswered
JOSEPHGILBY
asked this question in
Q&A
Replies: 1 comment 5 replies
-
I believe his is more todo with the VM running the container, although it could be an issue with rootless podman versus rootful podman, Have you tried this with rootful? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Contaner architecture summary (details shared below):
I've observed this issue on two separate Macs and not on podman running on Windows WSL. Basically, we're running a webserver over localhost inside the development container. Intermittently, but not always, the browser will fail to load a webpage because of
net::ERR CONTENT LENGTH MISMATCH
thrown for one of the static files (html, css, js). Taking a look at wireshark for one of these failed file downloads, the last pieces of data don't seem to have been sent at all. However, no indication of a failed download is sent and the FIN packets are sent and acknowledged in the transmission.The webserver we run is PHP's webserver. To debug the issue further, I installed PHP's source and modified the source to check and make sure every byte of the static file is read (POSIX read) from the filestore and then sent (POSIX send) to the network with no errors (<0 returned). As such, no errors were thrown and every byte of the static file was read and sent during a failed file download.
With this information, I'm not sure how to move forward. Are there any additional tools you might suggest to continue debugging this issue? Trying to read past POSIX read() and send() commands I run into the container's kernel which could mean the issue lies with Microsoft's dev container implementation, podman container / pod / machine implementation, or something else. At this time, i suspect the issue could lie in podman since the packet drops haven't been observed in Windows over WSL, but I'm not sure what tools I could use to continue looking at this issue. Any ideas?
podman pod inspect
(names scrambled)podman container inspect mssql
podman container inspect priceless_babbage
Output of
podman version
:Output of
podman info --debug:
Package info (e.g. output of
rpm -q podman
orapt list podman
):I ran
brew list podman
since the other two are not installed on my Mac.Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
I haven't personally tested on the latest Podman version, but someone else checked on the latest Podman version and the issue still occurred.
Additional environment details (AWS, VirtualBox, physical, etc.):
Beta Was this translation helpful? Give feedback.
All reactions