Arch Linux

Zmyrgel

Member

From: Finland

Registered: 2006-09-30

Posts: 31

[SOLVED] Podman crawls on "npm install" after upgrade to 5.0.0

Pretty odd issue, noticed that building container with podman gets "stuck" when running "npm install" command. This worked just fine last friday.
Using verbose output in the Dockerfile "npm install" command shows it installs the dependencies but takes couple of seconds for each transient dependency. I haven't waited this process to finish, at least 15 minutes is not enough for it to complete this step as of now.
For comparison running the "npm install" on local environment without using podman takes about 4 seconds to complete.

Downgrading podman from 5.0.0 to podman-4.9.3-1 seems to restore the container build process so it does not take too long in the "npm install" phase.

Any ideas what could cause such issue in the update?

Last edited by Zmyrgel (2024-03-27 12:29:53)

Zmyrgel

Member

From: Finland

Registered: 2006-09-30

Posts: 31

Re: [SOLVED] Podman crawls on "npm install" after upgrade to 5.0.0

Actually got it to work as expected by adding following to ~/.config/containers/containers.conf:

[network]
default_rootless_network_cmd="slirp4netns"

I guess the 5.0.0 version defaults to some newer network than the slirp4nets.

Xangelix

Member

Registered: 2024-03-27

Posts: 1

Re: [SOLVED] Podman crawls on "npm install" after upgrade to 5.0.0

Thank you for this-- I don't have the time right now to investigate further, but all outbound and inbound connections were failing for me and this resolved that. Pasta would not work and I couldn't find any relevant error messages.
If someone discovers a better way to handle this for now please provide it in the thread!

Last edited by Xangelix (2024-03-27 20:15:44)

Lithium Sulfate

Member

Registered: 2020-07-01

Posts: 16

Re: [SOLVED] Podman crawls on "npm install" after upgrade to 5.0.0

FYI, in case it's related; there has been a regression in podman 5.0.0 + pasta/passt that affected outbound network connectivity on some setups. This was fixed in passt 2024_03_26.4988e2b-1 which already hit the Arch repos yesterday, and it did fix these issues on my end.

You could try if the updated passt works for you as well in case you'd like to revert the network configuration change.