Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80267 - [podman] 4.7.2-1 gives connection error for yarn

Attached to Project: Arch Linux
Opened by fer plu (fermentedplums) - Thursday, 16 November 2023, 08:14 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 22 November 2023, 03:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Podman versions 4.4.3 through 4.7.2-1 cannot be used to build a yarn project inside a container(tested with just alpine).
When trying to run yarn install, the following error is given:
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/dependency-graph/-/dependency-graph-0.7.2.tgz: getaddrinfo EAI_AGAIN registry.yarnpkg.com registry.yarnpkg.com:443".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Trace:
Error: getaddrinfo EAI_AGAIN registry.yarnpkg.com registry.yarnpkg.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)


Steps to reproduce:

Follow podman wiki and install it.
Run an alpine container and enter it.
Install yarn and npm through apk.
Clone a yarn project.
Run yarn install to install all project's dependencies.
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 22 November 2023, 03:28 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Refer comments
Comment by Toolybird (Toolybird) - Thursday, 16 November 2023, 20:04 GMT
> Podman versions 4.4.3 through 4.7.2-1

So it's been like this for 7 months?

> Steps to reproduce:

Sorry, but you'll need to do better than this. You must assume that folks reading this ticket are not familiar with the subject matter at all. Please specify the *exact* steps to reproduce the problem and don't generalize.

Does it work if you use an Arch image instead of Alpine?

Anyway, at this stage I'm failing to see how foreign pkgs inside an Alpine image is somehow an Arch podman packaging issue. Stuff like this really belongs in the support channels (Forum/IRC/etc).
Comment by fer plu (fermentedplums) - Friday, 17 November 2023, 14:08 GMT
Ok, so I found a public project so anyone can reproduce the problem.

Steps:
1. Create a Dockerfile with the following contents:

FROM alpine:3.18.4
RUN apk add --no-cache git yarn
RUN git clone https://github.com/seanpmaxwell/express-generator-typescript.git
ENTRYPOINT [ "/bin/sh" ]

2. Create a docker-compose.yml with the following contents:

services:
relay:
build:
context: .
container_name: test
tty: true
stdin_open: true

3. Run podman-compose up -d
4. Run podman exec -it test sh
5. Run cd express-generator-typescript && yarn install

With an arch image, the above project seems to work, but I can't use arch image because I am working on a private project that is in an alpine image.

Now if these steps are done manually, the problem doesn't occur.

1. podman run -i -t alpine:3.18.4 sh
2. apk add --no-cache git yarn
3. git clone https://github.com/seanpmaxwell/express-generator-typescript.git
4. cd express-generator-typescript && yarn install

The only reason why I'm saying this is an Arch podman packaging issue is because I used podman 4.5.0 on Nixos 23-05 and podman 4.7.2 on Fedora 39 and the problem doesn't occur.
Comment by fer plu (fermentedplums) - Friday, 17 November 2023, 14:09 GMT
/
Comment by Toolybird (Toolybird) - Wednesday, 22 November 2023, 03:27 GMT
Thanks for the additional info.. but unfortunately I still couldn't get your instructions fully working (keeping in mind I'm not a podman user and don't really know what I'm doing...)

I did see an error at one point about a missing "aardvark-dns" binary.. and seeing as your original error is DNS related (Error: getaddrinfo EAI_AGAIN) I'm wondering if you have that pkg installed? (It is mentioned in the Wiki at [1]).

Anyway, there is still no evidence of this being an Arch packaging issue. Especially as it works when run "manually". Please take it to the support channels (Forum/IRC/etc) to see if anyone else can figure out what's going on.

[1] https://wiki.archlinux.org/title/Podman#Additional_dependencies

Loading...