Stephan Lüscher

I'd be interested for a solution on this topic as well. Is there a way to copy a collection during the build step?

I have the same issue under Ubuntu 20.04 with podman 3.0 with the ubuntu and the node container. Here the truncated output of **/etc/passwd** ``` $ cat /etc/passwd ... vscode:x:1000:1000::/home/vscode:/bin/bash...

When I set the **IMAGE_USER** to **vscode** in the **Dockerfile** with `ENV IMAGE_USER vscode` the container can be started but the permissions in **vscode** home directory are wrong. User /...

With `"containerUser": "vscode"` in the **devcontainer.json** file the container starts. But I still have the issue with the wrong permission set to **root:root** instead of **vscode:vscode**. ``` vscode ➜ /workspaces/ansible-dev...

Maybe the container has to be launched with `--userns=keep-id`. "We do recognize that this doesn't really match how many people intend to use rootless Podman - they want their UID...

et voilà ! That did the trick. Added the two lines to the **devcontainer.json** ``` "runArgs": ["--userns=keep-id"], "containerUser": "vscode" ``` Now the permissions are as expected: ``` vscode ➜ /workspaces/ansible-dev...

@EirikFA At least in my case your config snippet works with podman but fails with docker. Docker does not support `--userns=keep-id`

And the ciscoisesdk can't be installed in an ansible project which uses ansible-lint in a version newer than `6.16.1`. ```sh vscode ➜ /workspaces/cisco_ise_operation (release/1.0.0) $ poetry add ciscoisesdk Skipping virtualenv...

As I'm struggling with the same issue I was wondering if this feature has been implemented? According to #531 it was not merged because of code formatting issues? > Closing...

> > I've tired all of these solutions and none of them work, the WM class is set correctly, hostname is set correctly, the only thing I see is that...