BUG: Devcontainer running in Docker does not set UID

[jcox10]

After #364, the container is now running as root. The setting for a docker devcontainer "updateRemoteUserUID": true does not work for the root user, therefore all file ownership inside the container is not correct. Since the working directory is volume mounted, all files created will be owned by root on the host machine, instead of the UID of the user.

[jeffcpullen]

The .devcontainer files point at ghcr.io/ansible/community-ansible-dev-tools:v25.5.1 which run as root by default.

% podman run --rm -it ghcr.io/ansible/community-ansible-dev-tools:latest id
uid=0(root) gid=0(root) groups=0(root)

This is not the case with the DevSpaces version of the imageghcr.io/ansible/ansible-devspaces:v25.5.1

% podman run --rm -it ghcr.io/ansible/ansible-devspaces:v25.5.1 id     
WARNING: image platform (linux/amd64) does not match the expected platform (linux/arm64)

Kubedock is disabled. It can be enabled with the env variable "KUBEDOCK_ENABLED=true"
set in the workspace Devfile or in a Kubernetes ConfigMap in the developer namespace.

uid=10001(user) gid=10001(user) groups=10001(user),0(root),10(wheel)

I'm not sure if that is by design to have the default running as root or just hadn't been solved to run as a regular user yet. Perhaps now that the devspaces image has gotten it working it should be replicated in the devcontainer images.