Open ambis opened 1 year ago
The first things you should try is to use --network host
for you build command, this excludes all the podman networking setup. If it is still a problem with that option then it is in fact a problem with the network stack of the VM. I don't think it is possible to change the MTU right now in the VM.
Unfortunately podman build --network host ...
did not resolve this issue.
A friendly reminder that this issue had no activity for 30 days.
@ashley-cui @Luap99 Is this something we could do with podman machine?
@ambis Can you try setting the MTU in the VM with podman machine ssh sudo ip link set ens3 mtu 1380
and check if this works? You may need to switch the intefrace name, I don't know if this is consistent for all VMs.
I have no idea if qemu, gvproxy or others also need special handling for such mtu.
A friendly reminder that this issue had no activity for 30 days.
Not sure if this issue should be posted here or elsewhere.
Anyways, with M1 Macbook Pro and podman machine, I have this issue most likely with MTU.
I use VPN to access company resources (like NPM registries etc). While building a container (which succeeds with docker no problem) I get these random weird TLS/download issues. Build also succeeds in CI without problems (within the company network without VPN).
Often these issues get resolved by lowerin the MTU to something like 1380.
I'm asking if there is any way to set the MTU for the podman machine VM that does the build?
Note thata "podman network" has nothing to do this (AFAIK) since the build process does not happen within a podman network (again AFAIK).
Edit: running latest podman 4.5.0 via brew with a recreated VM.