-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
directfs startup issue #9356
Comments
Strange that the hello-world container won't start up. It seems that the |
Note to self: It might be because of the custom |
added the latest logfile |
A "broken pipe" error in urpc indicates that the |
these are the logs I have, just to clarify
runsc.log.20230910-092119.273955.create.txt |
looks like userns-remap is causing trouble
|
Thanks for the report, we understand the issue. We are working on a resolution. |
Description
When using directfs (starting from the june build) I am unable to start containers,
When disabling directfs using
--directfs=false
or using runsc from the may build, the container starts.Steps to reproduce
No response
runsc version
docker version (if using docker)
Client: Version: 24.0.5 API version: 1.43 Go version: go1.20.6 Git commit: ced0996600 Built: Wed Jul 26 21:44:58 2023 OS/Arch: linux/amd64 Context: default Server: Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.6 Git commit: a61e2b4c9c Built: Wed Jul 26 21:44:58 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.7.2 GitCommit: 0cae528dd6cb557f7201036e9f43420650207b58.m runc: Version: 1.1.9 GitCommit: docker-init: Version: 0.19.0 GitCommit: de40ad0
uname
Linux lolo 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/Linux
kubectl (if using Kubernetes)
No response
repo state (if built from source)
No response
runsc debug logs (if available)
The text was updated successfully, but these errors were encountered: