Arch Linux

tessaracht

Member

Registered: 2021-02-15

Posts: 10

official docker container is broken

hey all,

I'm trying to figure out how to report that the official arch docker container is broken when run on a host distro other than Arch:

```
$ uname -or
5.8.0-43-lowlatency GNU/Linux
$docker run -it archlinux bash
[root@87bd2b24bd50 /]# pacman -Syu
error: failed to initialize alpm library
(could not find or read directory: /var/lib/pacman/)
```

the dockerhub page says to report it to the arch gitlab (https://gitlab.archlinux.org/archlinux/ … ker/issues), but I can't see a way to actually sign up for that, it uses some SSO that doesn't hook into this forum account and doesn't have a registration option on the login page.

anyone know how you're actually supposed to file bugs on this thing? it works when run from Arch, so I imagine they've done something that isn't actually system independent.

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: official docker container is broken

https://hub.docker.com/_/archlinux

Four people are listed there, if you cannot find any other way of contacting them then there is always private email.

But the problem is https://bugs.archlinux.org/task/69563

glibc 2.33 poses challenges. The primary challenge at the moment is, probably, a version of docker/runc that is too old and doesn't include https://github.com/opencontainers/runc/pull/2750

There's nothing much to say IMO. Other distros will need to upgrade docker for critical compatibility fixes.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

tessaracht

Member

Registered: 2021-02-15

Posts: 10

Re: official docker container is broken

Ahhh I see that only got patched in a couple weeks ago. looks like the official Ubuntu PPA from docker is only one rc version behind the arch installed version, so hopefully that'll make its way into the PPA soon:

ubuntu$ runc -v
runc version 1.0.0-rc92
commit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
spec: 1.0.2-dev0

arch$ runc -v
runc version 1.0.0-rc93
commit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
spec: 1.0.2-dev
go: go1.15.7
libseccomp: 2.5.1

thanks for the tip on the upstream bugs! I'll keep an eye out for a new release of the containerd package and hopefully that'll sort everything out.

(also, I didn't just e-mail folks because as a dev i hate getting e-mails on stuff i maintain when there's a ticket system, but i guess if the folks who maintain the arch container are ok with it that's what i'll do from now on )

Last edited by tessaracht (2021-02-18 06:49:05)

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: official docker container is broken

(also, I didn't just e-mail folks because as a dev i hate getting e-mails on stuff i maintain when there's a ticket system, but i guess if the folks who maintain the arch container are ok with it that's what i'll do from now on )

If the ticket system is a gitlab instance that isn't open to the public, then you don't have much choice -- in *practice* there is no ticket system.

The devops team has been promising "soon" it will be opened to the public for a while now, but personally I would not migrate any projects there until "soon" becomes "it happened already". There is no guaranteed date...

Hence, my email suggestion.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)