Can you provide the podman commands that are used to build and run the image? What are the error messages you are seeing?

Do you use it on linux, macos, windows?

I'm on ArchLinux.

Last error is

mkdir: cannot create directory '/root': Permission denied
Exit code 1
Command in container failed: mkdir -p '/root/.vscode-server/bin' && ln -s '/vscode/vscode-server/bin/x64/{{hashA}}' '/root/.vscode-server/bin/{{hashA}}'

"remote.containers.dockerPath": XXX using one of below

• docker (rootful docker + usermod)
• podman
• sudo-podman

All of three under similar calling.

{{XXX}} build \
  -f /path/to/.devcontainer/Dockerfile \
  -t vsc-tmp.{{hash}} \
  --build-arg VARIANT=focal \
  /path/to/.devcontainer

...

{{XXX}} build \
  -f /tmp/vsch/updateUID.Dockerfile-0.191.1 \
  -t vsc-tmp.{{hash}}-uid \
  --build-arg BASE_IMAGE=vsc-tmp.{{hash}} \
  --build-arg REMOTE_USER=vscode \
  --build-arg NEW_UID=1000 \
  --build-arg NEW_GID=1000 \
  --build-arg IMAGE_USER=root \
  /tmp/vsch

docker (rootful docker + usermod)

Start: Run in container: test -d /home/vscode/.vscode-server
Start: Run in container: test -d /home/vscode/.vscode-remote
...

podman

Start: Run in container: test -d /root/.vscode-server
Start: Run in container: test -d /root/.vscode-remote
...

sudo-podman

Start: Run in container: test -d /root/.vscode-server
Start: Run in container: test -d /root/.vscode-remote
...

First are you running both in rootful mode?
@flouthoc PTAL

@rhatdan

Log updated.

OK in rootful docker + usermod.

Fail in both podman and sudo-podman

Plus, does below affect build or just shell?

It's the only kind of warning appear in podman and sudo-podman situation.

STEP 6/9: SHELL ["/bin/sh", "-c"]
WARN[0007] SHELL is not supported for OCI image format, 
[/bin/sh -c] will be ignored. Must use `docker` format

Use --format docker, to not use OCI Format.

On devcontainer you also need to specify the containerUser, something like this:

	"runArgs": [
		"--userns=keep-id"
	],
	"remoteUser": "vscode",
	"containerUser": "vscode"

Because I uses bind mount for the code, I need to add --userns=keep-id to access the user in vscode. I uses my default UID and UGID of 1000, which is the same as the vscode user inside the container, so the command map the vscode user inside the container to my user outside. If you run without that options, the bind-mounted files will be inaccessible.
Do note that I disable SELinux, so I'm not sure how it would interact with bind mounting.
Reference: https://blog.lifeishao.com/2021/12/30/replacing-docker-with-podman-for-your-vscode-devcontainers/

Ah, get it working.

settings.json

  "remote.containers.dockerPath": "podman-devcontainer-wrapper",
  // "remote.containers.dockerComposePath": "podman-compose-devcontainer-wrapper"

devcontainer.json

    "remoteUser": "vscode",
    "containerUser": "vscode"

podman-devcontainer-wrapper

BUILDAH_FORMAT=docker \
PODMAN_USERNS=keep-id \
podman "$@"

ref

• https://docs.podman.io/en/latest/markdown/podman-build.1.html#format
• https://docs.podman.io/en/latest/markdown/podman-create.1.html#userns-mode