Closed aleksanderostrup closed 1 year ago
using podman and podman-compose the same problem happens
[2022-10-17 23:51:10.464] [exthost] [error] {"message":"Command failed: /home/alex/.vscode-server/bin/d045a5eda657f4d7b676dedbfa7aab8207f8a075/node /home/alex/.vscode-remote-containers/dist/dev-containers-cli-0.255.4/dist/spec-node/devContainersSpecCLI.js read-configuration --docker-path podman --docker-compose-path podman-compose --workspace-folder /home/alex/development/test-api --log-level debug --log-format json --config /home/alex/development/test-api/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root true","code":1} remote-containers.openFolder {"value":"ms-vscode-remote.remote-containers","_lower":"ms-vscode-remote.remote-containers"}
running the command directly to understand the error, I have this output:
$ /home/alex/.vscode-server/bin/d045a5eda657f4d7b676dedbfa7aab8207f8a075/node /home/alex/.vscode-remote-containers/dist/dev-containers-cli-0.255.4/dist/spec-node/devContainersSpecCLI.js read-configuration --docker-path podman --docker-compose-path podman-compose --workspace-folder /home/alex/development/test-api --log-level debug --log-format json --config /home/alex/development/test-api/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root true
(node:19830) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Error: Missing node-pty
at gD (/home/alex/.vscode-remote-containers/dist/dev-containers-cli-0.255.4/dist/spec-node/devContainersSpecCLI.js:1666:1412)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async un (/home/alex/.vscode-remote-containers/dist/dev-containers-cli-0.255.4/dist/spec-node/devContainersSpecCLI.js:1665:13306)
at async _ae (/home/alex/.vscode-remote-containers/dist/dev-containers-cli-0.255.4/dist/spec-node/devContainersSpecCLI.js:1994:25824)
I think that it might be related to permission rights, but I'm not sure.
Are all the Dockerfile commands being executed as root? Or maybe this has changed, which is the cause of the problem.
@aleksanderostrup I'm running my containers without root privileges, with Rootless Podman, I can't tell from the error messages if it's a permissions problem, the error I can see in the console is this: Error: Missing node-pty
Is there any way to debug this kind of problem?
Not that I know of. Hopefully one of the devs will take a look at this in due time.
The base images now pass down the "remoteUser"
config (among other properties). Try setting it explicitly to root
if you don't set it in your devcontainer.json to some other user by adding "remoteUser": "root"
. Does that help?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Steps to Reproduce:
RUN usermod -l ${USERNAME} vscode --home /home/${USERNAME} --move-home
(where the ${USERNAME} is defined) breaks the building of the container. It has worked previously with version 0.224.3 of Dev Containers.This might be related to https://github.com/microsoft/vscode-remote-release/issues/6525.
I have tried with the pre-release version of the extension, but that does not seem to fix the issue either.
For some reason I cannot upload my *.log file, so here is the crucial part: