Cotainr devcontainer

[Chroxvi]

A devcontainer.json for cotainr with a focus (for now) on VS Code with podman.

Also sets a few environment variables in the Dockerfile which are useful for both the dev conatiner setup and the Makefile setup.

[joasode]

When I open up that PR in my vscode, the terminal spams bash: history: /commandhistory/.bash_history: cannot create: Permission denied with every terminal command, is this expected behavior?

[joasode]

As far as I can see, at least one of these three settings are currently mandatory in settings.json for our tests to pass, maybe we should have a short section in the documentation for these details?

    "containers.containerClient": "com.microsoft.visualstudio.containers.podman",
    "containers.containerCommand": "podman",
    "containers.composeCommand": "podman-compose"

[Chroxvi]

@joasode Did you test with docker (not podman)? I am a little worried about the bash: history: /commandhistory/.bash_history: cannot create: Permission denied issue. I wonder if that is specific to docker?

As we agreed in one of our check-ins, I only cared about podman when setting it up. Hence, in my settings.json, I have "dev.containers.dockerPath": "podman" which I believe should be sufficient to run using podman. And, yes, you most likely need more securityOpt flags to run using docker - as is currently hinted in the devcontainer.json comments. But you are right that we need to document all of this. It needs to be coordinated with the documentation related to #139, so @TheBlackKoala and I agreed to do a follow-up PR with documentation for both of these PRs.

[joasode]

@Chroxvi I tested it again, and indeed it seems like this was an error when I was still using docker and not anymore after I changed to podman.

[Chroxvi]

Alright, then I think the bash: history: /commandhistory/.bash_history: cannot create: Permission denied issue is related to microsoft/vscode-remote-release#9931. It seems that it is only a problem when using Docker. At least setting containerUser to the non-root user solved the problem for me when using podman. I guess we'll just leave it at that for now. I can link the issue in the comments in the devcontainer.json and then we can just mention in the documentation that the devcontainer is (for now) only supported with podman.

[juliusroeder]

Hi,
I am just trying this.
I added the dockerPath stuff to my settings list and I get the following errors.
Any idea what that is about?

[joasode]

I think it looks good. (assuming that documentation of this VScode setup follows later)

[Chroxvi]

The documentation is in this branch: main...dev_env_docs along with lots of other documentation updates. A PR is expected today or tomorrow. The VSCode documentation include a disclaimer about the dev container setup still being experimental since we are seeing so many issues with permissions for different combinations of OS'es, container runtimes, and versions of the VSCode dev container extension.

@juliusroeder's issue is reported upstream: microsoft/vscode-remote-release#11042

I will try to make a similar report for the VSCode dev container v0.417.0 regression, I have encountered.