Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start without remoteUser defined to "root" #11

Open
rclsilver opened this issue Nov 4, 2024 · 0 comments
Open

Unable to start without remoteUser defined to "root" #11

rclsilver opened this issue Nov 4, 2024 · 0 comments

Comments

@rclsilver
Copy link

rclsilver commented Nov 4, 2024

Hi,

With the following container configuration, I'm unable to start it unless I define the remote user to "root":

{
  "name": "backup-controller",
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
  "features": {
    "ghcr.io/devcontainers/features/go": {},
    "ghcr.io/devcontainers/features/docker-outside-of-docker": {},
    "ghcr.io/devcontainers/features/kubectl-helm-minikube": {
      "version": "latest",
      "helm": "latest",
      "minikube": "none"
    },
    "ghcr.io/microsoft/devcontainers/features/k3s-on-host": {
      "k3sVersion": "latest",
      "criDockerd": "true",
      "cluster_enabled": "true"
    }
  }
}

Is it the expected behavior? The problem with that is that all the created files are owned by root :( You can find find here the log: remoteContainers-2024-11-04T06-56-35.748Z.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant