Latest docker doesn't start

[manuc66]

When starting the container, no log is produced and it is stuck somewhere in the init procedure before showing this

node-hp-scan-to/root/etc/cont-init.d/10-adduser

Line 10 in c591df2

User uid: $(id -u node)

Command line used:
docker run -e IP=192.168.1.53 -e CMDLINE=-D manuc66/node-hp-scan-to:latest

The log received

latest: Pulling from manuc66/node-hp-scan-to
2408cc74d12b: Already exists 
8283096dcba0: Already exists 
a3e654983208: Already exists 
024c9a3b77d6: Already exists 
06af66291f17: Pull complete 
4ca063587d57: Pull complete 
4a82ea43390b: Pull complete 
bd2096739089: Pull complete 
dc9d35495c02: Pull complete 
91319420c052: Pull complete 
8989054a3d87: Pull complete 
Digest: sha256:9b9165a48c940dbc3e8993af2b0522a60d52b3e742c1b01045e2457b8b8d93df
Status: Downloaded newer image for manuc66/node-hp-scan-to:latest

[manuc66]

@charlie89 Do you have an idea on what's going on ?

[manuc66]

When launching the container from windows (WSL2 backend) it works fine:

>docker run manuc66/node-hp-scan-to
Unable to find image 'manuc66/node-hp-scan-to:latest' locally
latest: Pulling from manuc66/node-hp-scan-to
2408cc74d12b: Pull complete
8283096dcba0: Pull complete
a3e654983208: Pull complete
024c9a3b77d6: Pull complete
06af66291f17: Pull complete
4ca063587d57: Pull complete
4a82ea43390b: Pull complete
bd2096739089: Pull complete
dc9d35495c02: Pull complete
91319420c052: Pull complete
8989054a3d87: Pull complete
Digest: sha256:9b9165a48c940dbc3e8993af2b0522a60d52b3e742c1b01045e2457b8b8d93df
Status: Downloaded newer image for manuc66/node-hp-scan-to:latest
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/10-adduser

User uid:    911
User gid:    911
-------------------------------------

s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
Target folder: /scan
Temp folder: /tmp/scan-to-pcadgmPf
Running iteration: 0 - errorCount: 0
Host destinations fetched: xxxxxx
New Destination registered: 4735ca5488a8 - /WalkupScanToComp/WalkupScanToCompDestinations/664ac3e5-ba46-4136-b112-571c69be8333
Using: 4735ca5488a8
Waiting scan event for: /WalkupScanToComp/WalkupScanToCompDestinations/664ac3e5-ba46-4136-b112-571c69be8333
Start listening for new ScanEvent

and we have those warnings:

s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out

[manuc66]

Top shows this:

    PID UTIL.     PR  NI    VIRT    RES    SHR S  %CPU  %MEM    TEMPS+ COM.                                                                                                                                        
   7081 root      20   0     448    100     72 R  99,7   0,0   9:40.55 s6-ftrigrd 

ps aufx gives

root        7034  0.0  0.0    200    60 ?        Ss   21:22   0:00  \_ /package/admin/s6/command/s6-svscan -d4 -- /run/service
root        7074  0.0  0.0   1604   956 ?        Ss   21:22   0:00      \_ /bin/sh -e /run/s6/basedir/scripts/rc.init top /app.sh
root        7080  0.0  0.0    232   108 ?        S    21:22   0:00      |   \_ s6-rc-init -c /run/s6/db /run/service
root        7081 99.7  0.0    448   100 ?        R    21:22   8:05      |       \_ /package/admin/s6/command/s6-ftrigrd
root        7075  0.0  0.0    204    64 ?        S    21:22   0:00      \_ s6-supervise s6-linux-init-shutdownd
root        7077  0.0  0.0    192     4 ?        Ss   21:22   0:00          \_ /package/admin/s6-linux-init/command/s6-linux-init-shutdownd -c /run/s6/basedir -g 3000 -C -B

And top inside the container shows this:

Mem: 9893016K used, 6357228K free, 1091340K shrd, 378612K buff, 4539444K cached
CPU:   5% usr   8% sys   0% nic  85% idle   0% io   0% irq   0% sirq
Load average: 2.50 2.09 1.89 3/1632 53
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
   21    20 root     R      448   0%   3  13% /package/admin/s6/command/s6-ftrigrd
   22     0 root     S     1672   0%   6   0% sh
   14     1 root     S     1604   0%   1   0% {rc.init} /bin/sh -e /run/s6/basedir/scripts/rc.init top /app.sh
   53    22 root     R     1600   0%   6   0% top
   20    14 root     S      232   0%   5   0% s6-rc-init -c /run/s6/db /run/service
   15     1 root     S      204   0%   3   0% s6-supervise s6-linux-init-shutdownd
    1     0 root     S      200   0%   6   0% /package/admin/s6/command/s6-svscan -d4 -- /run/service
   17    15 root     S      192   0%   0   0% /package/admin/s6-linux-init/command/s6-linux-init-shutdownd -c /run/s6/basedir -g 3000 -C -B

[manuc66]

It seems to be related to just-containers/s6-overlay#456