.devcontainer points to internal Docker image

[aspctu]

The .devcontainer currently points to

urm.nvidia.com/sw-tensorrt-docker/tensorrt-llm:pytorch-25.01-py3-x86_64-ubuntu24.04-trt10.8.0.43-skip-devel-202503131720-8877

which isn't publicly accessible. Is there a public mirror that we can point this that external devs can also access?

[juney-nvidia]

@MartinMarciniszyn for vis.

• @zeroepoch @chzblych @mk-nvidia for vis.

@aspctu
Hi, we are working to publish pre-built containers to the public to ease the efforts of community usage, and it will still take time.
When it gets done, we will keep the community posted.

Thanks
June

[karljang]

@aspctu ,
The scripts in .devcontainer appear to have been designed to support the following overriding mechanism:

Create a file named .devcontainer/devcontainer.env.user with the following content:

DEV_CONTAINER_IMAGE=nvcr.io/nvidia/tensorrt-llm/release:1.2.0

Once this file is created, the Reopen in Container option in VS Code will function as follows:

   devcontainer.json
        ↓
   "initializeCommand": ".devcontainer/make_env.py"  ← Runs FIRST
        ↓
   make_env.py creates .devcontainer/.env with DEV_CONTAINER_IMAGE
        ↓
   docker-compose.yml uses ${DEV_CONTAINER_IMAGE}
        ↓
   Container starts with all extensions, settings pre-configured

I didn’t have the opportunity to try it myself. Please let us know if it works or not so that we can close the issue.

[MartinMarciniszyn]

Instead of

DEV_CONTAINER_IMAGE=nvcr.io/nvidia/tensorrt-llm/release:1.2.0

I suggest trying one of the public development images. For example:

DEV_CONTAINER_IMAGE=nvcr.io/nvidia/tensorrt-llm/devel:1.2.0rc5