Skip to content

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

@rclsilver

Description

@rclsilver

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions