directfs startup issue about gvisor HOT 7 OPEN

looks like userns-remap is causing trouble

$ docker run --userns=host --rm --runtime=runsc-debug hello-world

Hello from Docker!

from gvisor.

Strange that the hello-world container won't start up. It seems that the start command is failing. Could you upload the logs from that command? The resultant log file will have the start suffix in it. I think the above mentioned logs are from the create command, which was successful.

from gvisor.

Note to self: It might be because of the custom uidMappings and gidMappings set in the container spec.

from gvisor.

added the latest logfile

runsc.log.20230909-162304.911145.start.txt

from gvisor.

A "broken pipe" error in urpc indicates that the runsc start command failed to communicate with the runsc boot process, for example if the runsc boot process crashed while handling the request to start the container. Can you upload the *.boot.log log? (Or simply upload every log you have.)

from gvisor.

these are the logs I have,

just to clarify

• all other containers fail to startup.
• userns-remap and no-new-privileges are enabled
• userland-proxy is disabled
• storage-driver is overlay2

runsc.log.20230910-092119.273955.create.txt
runsc.log.20230910-092119.343513.gofer.txt
runsc.log.20230910-092119.349445.boot.txt
runsc.log.20230910-092119.749576.start.txt
runsc.log.20230910-092119.850217.kill.txt

from gvisor.

Thanks for the report, we understand the issue. We are working on a resolution.

from gvisor.