Docker build freezes for manjarolinux/base

Manjaro-Development Manjaro Docker
#1

A lil help guys…

the docker build freezes on:

(1/6) Creating system user accounts...
Creating group git with gid 977.
Creating user git (git daemon user) with uid 977 and gid 977.
(2/6) Reloading system manager configuration...
  Skipped: Current root is not booted.
(3/6) Creating temporary files...
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping
All rules containing unresolvable specifiers will be skipped.

dockerfile:

FROM manjarolinux/base

RUN pacman-mirrors -g
RUN pacman -Syy
RUN	rm -fr /etc/pacman.d/gnupg 
RUN	pacman-key --init 
RUN pacman-key --populate archlinux
RUN pacman-key --populate manjaro
# RUN pacman-key --refresh-keys
RUN	pacman -Syyu --noconfirm
RUN pacman -S --noconfirm gnupg
RUN pacman -Fyy --noconfirm

RUN pacman -Sy --noconfirm vim git gzip yay
RUN pacman -Sy --noconfirm sudo fakeroot make

RUN pacman -Sy --noconfirm gcc clang 

RUN groupadd sudo wheel
RUN useradd -m -d /home/manjarouser -s /bin/zsh -g sudo wheel manjarouser

USER manjarouser
#2

@kesarling: same on my side.
I have been using / updating images based on this image for over a year now and now it fails all of a sudden. Any progress on resolving it?

#3

@kesarling: it seems to be a bug in the 5.10 kernel!?
Have you tried with kernel 5.9 already?
I can now build the image again with the previous kernel, then boot back to 5.10 and use the image. It is a workaround, but at least keeps my infrastructure running.

#4

I just retested with the latest kernel 5.10.7 from the testing branch, as I was hoping that LWN LXC broken with 5.10-stable?, ok with 5.9-stable was the reason for it, but it unfortunately still stalls affecting the docker daemon. A reboot is required to make it work again :frowning: , restarting the docker unit and killing all related process does not help.

Rebuilding images using kernel 5.9.16 works just fine.
@codesardine Any ideas?

#5

A new image of manjarolinux/base (76710bd87296) was just released recently. Now the error does not occur anymore.
There obviously was an issue within the base image before.

#6