Closed Freberg closed 2 months ago
Hey @Freberg, thanks for opening the issue. You're right that hasn't been something we've been looking into so far, we'll investigate
Hello @pascalbreuninger, thank you for confirming
If anyone else run into this issue, here is my current workaround:
on the server, allow users to set TMPDIR over ssh
sudo sed -i '/^AcceptEnv/ s/$/ TMPDIR/' /etc/ssh/sshd_config
on the client, set both AGENT_PATH and TMPDIR in the provider
devpod provider add ssh --name <PROVIDER_NAME> \
-o HOST=<USER>@<HOST> \
-o AGENT_PATH=./tmp/devpod/agent \
-o EXTRA_FLAGS='-o "SetEnv=TMPDIR=./tmp"'
What happened?
Using devpod with the ssh-provider works nicely for a single user, however when multiple users try to use the same server, permission issues are encountered as files in the /tmp/ directory will be owned by the user who first created a devcontainer.
The first issue occurs when the devpod agent is installed on the server:
debug Inject Error: Error: failed to install devpod
Above can be circumvented by setting AGENT_PATH=./tmp/devpod/agent to ensure ownership of the agent for each user. However, when adding features to the devcontainer the issue reappears, devpod seemingly does not provide a way to override below path.
info mkdir /tmp/devpod/features: permission denied
What did you expect to happen instead?
I expect devpod to handle multiple users on the same server by default.
How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:
DevPod Provider:
Anything else we need to know?
My current workaround is to set both AGENT_PATH in devpod and add TMPDIR to AcceptEnv in the sshd config and have the users pass TMPDIR=~/tmp in their ssh config.