Repository navigation
Can't find some files in /tmp #92
Description
Hi,
Thanks for creating this. Super helpful. I'm getting some warnings that I'm not sure how to resolve.
Checking for SSH_AUTH_SOCKWarning: Failed to get SSH_AUTH_SOCK value: docker exec error: exit status 2 (ls: cannot access '/tmp/vscode-ssh-auth-*': No such file or directory)
Continuing without setting SSH_AUTH_SOCK...
Getting code server pathWarning: Failed to get VS Code server location: docker exec error: exit status 2 (ls: cannot access '/vscode/vscode-server/bin/x64/*': No such file or directory)
Continuing without adding VS Code Server to PATH...
Getting REMOTE_CONTAINERS_IPCWarning; Failed to get REMOTE_CONTAINERS_IPC: docker exec error: exit status 2 (ls: cannot access '/tmp/vscode-remote-containers-ipc-*': No such file or directory)
Continuing without setting REMOTE_CONTAINERS_IPC...
Getting VSCODE_GIT_IPC_HANDLEWarning; Failed to get VSCODE_GIT_IPC_HANDLE: docker exec error: exit status 2 (ls: cannot access '/tmp/user/1001/vscode-git-*': No such file or directory)
Continuing without setting VSCODE_GIT_IPC_HANDLE...
Starting exec session
I'm using cursor and I don't have many vscode-* files. I have some of the following: (I use this devcontainer remotely via ssh).
cursor-remote-ssh-*.sock
vscode-git-*.sock
vscode-ipc-*.sock
How do I control what looks for these files?
Thanks.
Activity
whoopsmith commentedon Mar 31, 2026
I'll add that if I use the reference devcontainer CLI that those messages don't show up and ssh works whereas in devcontainerx ssh doesn't work.
stuartleeks commentedon Apr 2, 2026
Hi @whoopsmith,
Sorry you're having issues.
A couple of quick questions
devcontainer(official) CLI?Thanks!
whoopsmith commentedon Apr 2, 2026
No worries. Thanks for the response.
We use cursor. Which I think may be part of the issue as some of the files with vscode in the name don't exist. The container is normally started by cusor but now that I have the official devcontainer CLI working I can use it to start the container as well. So its both.
I don't have any prior usage of devcontainerx (I started with this project first before trying devcontainer CLI) so these errors have existed for me from the beginning. Would you like me to try a prior version and see if they go away?
stuartleeks commentedon Apr 2, 2026
Ah, ok. I started this project before the official CLI was released. I still use it for a bunch of VS Code integration (e.g.
devcontainerx open-in-codeto launch straight into VS Code as a dev container).The paths that it is looking for are for things that the VS Code extension sets up. AFAIK, these aren't things that the devcontainer CLI configures. When I started the project, the only way to spin up the dev container was VS Code, so this wasn't an issue. But now, maybe there should be a way to suppress the attempted VS Code integrations?