-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
devcontainers in vscode 1.86 no longer start when using an unprivileged remoteUser #204152
Comments
Please append the Dev Containers log from when this happens. ( |
Any relation to #203964? |
I've used vscode insiders for getting the log output, but it's the same for the actual release! As mentioned, we use an unprivileged
|
@deepak1556 This looks like another case to handle in the requirements script: |
Still failing |
Please check if the issue is present with latest insiders and pre-release version of the devcontainers extension. We have made some changes to install stage as part of #206790 which might address the issue here. |
Version: 1.88.0-insider With this version it's still failing |
Hey @deepak1556, this issue might need further attention. @scalpel4k, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
With the vscode 1.86 update devcontainers that are started with a non-root
remoteUser
do not start.During container start some script tries to run
sbin/ldconfig
which of course saysPermission denied
.Installing older devcontainer extensions doesn't solve the problem.
Although I haven't tested yet, this should also be problematic with Alpine based containers since there ldconfig doesn't even exist.
We had to revert to vscode 1.85.2 which fixed the problem for us, for now.
The text was updated successfully, but these errors were encountered: