You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vscode devcontainer uses root, which can lead to permission issues when also interacting with the repo/code locally.
Expected behavior
I want to be able to edit files locally and also commit locally and not only in the devcontainer, because I might have some tooling which is easier to use locally on the host and not in the container.
Current behavior
Currently, our devcontainer is running as root, which makes handling of a lot of things quite a bit easier during setup.
But it leads to the issue, that when commiting/editing all changes of the mounted directory will be done as the root user.
This leads to inability to commit or interact with the code locally without also using the root user on the host.
Possible Solution
Setup of user in Dockerfile with "$(id -u):$(id -g)" and setup of passwordless sudo access in /etc/sudoers or /etc/sudoers.d/*
The text was updated successfully, but these errors were encountered:
Summary
The vscode devcontainer uses root, which can lead to permission issues when also interacting with the repo/code locally.
Expected behavior
I want to be able to edit files locally and also commit locally and not only in the devcontainer, because I might have some tooling which is easier to use locally on the host and not in the container.
Current behavior
Currently, our devcontainer is running as root, which makes handling of a lot of things quite a bit easier during setup.
But it leads to the issue, that when commiting/editing all changes of the mounted directory will be done as the root user.
This leads to inability to commit or interact with the code locally without also using the root user on the host.
Possible Solution
Setup of user in
Dockerfile
with"$(id -u):$(id -g)"
and setup of passwordless sudo access in/etc/sudoers
or/etc/sudoers.d/*
The text was updated successfully, but these errors were encountered: