JulianFlesch

Note: This still uses (a newer) gitpod base image and thus also the `gitpod` user.

Changing this PR back to Draft to explore different base images: This compares the [Dockerfiles in `nf_core/devcontainer/`](https://github.com/JulianFlesch/nf-core-tools/tree/issues/3466-gitpod/nf_core/devcontainer). Currently the PR is a work in progress set up to use the...

Do you have an opinion on the base images and how we use docker @mashehu @mahesh-panchal ? Or should I just go with the smallest? Also: Do we want /...

> Ideally it should be as small as possible. I think the priority is to minimize how much maintenance we need to do our side so as long as the...

Ok I will just refine the solution with devcontainers then and ping you for a review. For one I am not sure that docker-outside-of-docker will even work on codespaces and...

@ewels Yep, devcontainer `features` are great! We are using those and docker-in-docker works like a charm on codespaces 🚀 (We are now using mcr.microsoft.com/devcontainers/python:3.11) I can add conda and nextflow...

Our image for use with devcontainer is now based on `ghcr.io/nextflow-io/training:latest` to remove a lot of redundancy and hopefully maintenance effort. The [setup.sh](https://github.com/JulianFlesch/nf-core-tools/blob/issues/3466-gitpod/.devcontainer/setup.sh) had to be added to make that...

Major Updates here: * After more discussion, we decided to move away from the `vscode` user and also use `root`. Most importantly because: - The vscode user already must already...

ToDo is updating the workflows. @mashehu do we want to keep pushing our own image? (That would obviously remove redundancy e.g. in modules and the template) or is it acceptable...

I'm currently doing extensive testing to check that the Github workflows _correctly_ build our devcontainers. This seems to go well for the most part, except I noticed the installation of...