Open matifali opened 5 months ago
While we're at it, I'd like to change the naming scheme:
images/base/ubuntu.Dockerfile
-> ubuntu:base
images/minimal/ubuntu.Dockerfile
-> ubuntu:minimal
images/$IMAGE/$DISTRO.Dockerfile
-> $DISTRO:$IMAGE
This might entail some shuffling things around on-disk.
Hi Team, I want to use nvidia base image for a template to perform some Deep learning and GPU based tasks. I have build the docker image with base nvidia/cuda:12.2.0-base-ubuntu22.04 and on top of that I have added curl and wget to run startup scripts and to download some dependencies. When I use that image in the template, While I'm launching the workspace I'm not able to launch it.
Please help me in this issue. Thanks.
The scope of the images in this repo does not cover every use case. cc: @bpmct
Hi, @PraveenkumarLilly. To use GPU, you also need a few other steps; please look at the deep learning templates and the source code for dockerdl images below to get the idea.
hi @PraveenkumarLilly - if you are having issues with Coder or Coder workspaces, we recommend you open an issue in #coder/coder
Hi @matifali, Thanks for replying back, We are using Kubernetes based template. Can you share Nvidia base GPU image in Kubernetes?
Hi @ericpaulsen, Sure, Eric I'll do that
Thanks.
While we're at it, I'd like to change the naming scheme:
images/base/ubuntu.Dockerfile
->ubuntu:base
images/minimal/ubuntu.Dockerfile
->ubuntu:minimal
images/$IMAGE/$DISTRO.Dockerfile
->$DISTRO:$IMAGE
This might entail some shuffling things around on-disk.
@jatcod3r, We are going to adopt the above convention for naming new and old images.
I like the new convention 👍🏼
I renamed the repo.
Can someone else help with the repo/image/pipeline format?
@johnstcn, do you also want images to be renamed or only the directory structure?
For images codercom/enterprise-base
--> codercom/base
?
@johnstcn, do you also want images to be renamed or only the directory structure?
For images
codercom/enterprise-base
-->codercom/base
?
I'm fine with keeping the current names of the published images. Renaming them would be a bit more involved and require communications. If we really feel like we want to rename the published images as well, we could dual-publish under both naming conventions with a deprecation period.
Huge fan of dual-publishing so we have a nice clean image for new users/examples. Down the road, we could use a motd or something to let people know we'll stop dual-publishing
We plan to publish new images on ghcr. Will add a MOTD to dockerhub ones and then stop them eventually
I am unfamiliar with why these images are called
enterprise-xxx
. We should probably rename the repo and images tocoder/images
. We can keep the legacy images on dockerhub and publish the new ones ghcr.ioThe idea is to have something like
coder/modules
andcoder/templates
and integrate with https://registry.coder.com where we can list images too. We can also accept community contributions for templates and images as we do with modules and list on our registry.cc: @bpmct