So I edited a few dockers and have committed the changes to new images.

 

I can run them from the command line and all works as I want but I can not get them added to the GUI outside of it automatically pulling the running docker in but it does not give me any options to edit said docker.

 

I tried manually creating a docker template but it insists on adding :latest to the image and that of course fails.

 

So 2 questions:

 

1: Is it possible to automatically create a template for the image with the information pre-filled?

 

2: How can I set the repository to a local image only with no tags?

Not sure if this is the best method but after some testing I realized you can tag local images with docker, I simply tagged the local image with the "containername:latest" tag and now it seems to work.

 

I used the info from this link to figure it out : https://ropenscilabs.github.io/r-docker-tutorial/04-Dockerhub.html

Edited February 22, 20215 yr by TexasUnraid

If you are commiting the image to the same repo/image name as the original container I would recommend using a different tag. Such as 'mylatest'. So you dont end up pulling the real latest image and blowing away your tag (unintentionally you can always retag things if you want). Using other tags in docker templates works just fine. A repo/image with no tag however defaults to the latest tag, not sure whether that is built into unRAID's implementation or docker itself.

3 minutes ago, primeval_god said:

If you are commiting the image to the same repo/image name as the original container I would recommend using a different tag. Such as 'mylatest'. So you dont end up pulling the real latest image and blowing away your tag (unintentionally you can always retag things if you want). Using other tags in docker templates works just fine. A repo/image with no tag however defaults to the latest tag, not sure whether that is built into unRAID's implementation or docker itself.

Good point, I was making a "new" docker with a python base docker, so this was not an issue for me as it was named completely different.

 

I could see forgetting that and having an issue if I was simply editing the docker of and leaving the name the same.