Replies: 1 comment
-
Yeah, a number of developer tools do not like running as root. This is why all of the pre-built devcontainer images include a non-root user. So the error you see is exactly right.
The "ghcr.io/devcontainers/features/common-utils" feature is intended to be an easy way to add a non-root user and tools developers tend to prefer using like man pages. You'll note this is referenced in all the devcontainer.json files used to build the mcr.microsoft.com images. You can then reference this non-root user as the |
Beta Was this translation helpful? Give feedback.
-
I was looking at getting a devcontainer together where I could run
minikube
on aPython
devcontainer as an experiment. I generated thedevcontainer.json
using VSCode which produced the following.Minikube starts up without a problem.
Debian Python Bullseye
Now if I switch the image to **
python:3.11-bullseye
.This yields the following error message:
I guess there are some subtle differences in the choice of image. In other experiments I've used the
python:3.11-bullseye
image to add some customisation into a dockerfile without any major issues.Ideally I want to control my environment as much as possible, but what considerations do you apply when selecting a devcontainer base image?
Ideally I would like to have:
With my choice of VSCode extensions (but the features install those). It would be cool to omit extension installation in the JSON (if we cannot already).
Where I can route calls from my Host OS Browser through to a FastAPI running in Minikube inside the devcontainer.
Beta Was this translation helpful? Give feedback.
All reactions