Docker "image already present" failure

[GoW]

I've hunted this forum and find items that are close to this.. but some seemingly too old so I can't get them to apply (or I'm misreading them). I have had an issue where I had to pull an installation of Sonarr and re-install it. So, I deleted Sonarr (using the three dots, selected both items to "delete") deleted.

Then go to applications, choose TrueCharts Sonarr, and upon install I receive these messages:

Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:323ab7aa3e7ce84c024df79d0f364282c1135499298f54be2ade46508a116c4b" already present on machine

Followed by:

Back-off restarting failed container

And then it just fails, sticking in the "Deploying" mode. I've left it sit in deploying overnight and it never rectifies itself. I'm not sure the best way to proceed.

 

[jkamther58]

Bump...same issue.

 

[sretalla]

Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:323ab7aa3e7ce84c024df79d0f364282c1135499298f54be2ade46508a116c4b" already present on machine

That's not an error, it's just information.

Back-off restarting failed container

That's giving you a clue as to what's going on... but really, you need to look at the container logs to see why it's not starting properly.

 

[VladTepsll]

Possible solution to this problem would be to manually delete the existing container image. I have had same problem a few times in past and i am not very good with Kubernetes. Dont know if this would help at all.

 

[alishakihnh]

The error message "image already present" in Docker typically occurs when you attempt to pull an image from a registry that you have already downloaded and pulled previously. Docker keeps track of the images it has downloaded, and if you try to pull the same image again, it will show this error.
Here are a few possible scenarios and solutions to resolve this issue:
1. Docker already has the image locally: If Docker has already downloaded the image you are trying to pull, you can simply use the existing local image instead of pulling it again. You can check your local images using the `docker images` command and then use the existing image in your Docker commands.
2. Tag mismatch: Ensure that you are using the correct image tag when pulling the image. If you specify a different tag that doesn't exist in the registry, Docker assumes you want to pull the latest version of the image. However, if you already have the latest version locally, it will show the "image already present" error. Double-check the tag you are using and make sure it matches the desired version.
3. Docker cache: Docker uses a caching mechanism to speed up image pulls. Sometimes, the cache may cause issues when pulling images. You can try clearing the Docker cache using the `docker builder prune` command, which removes all the dangling build cache.
4. Registry authentication: If you are using a private registry that requires authentication, ensure that you have logged in successfully before attempting to pull the image. Use the `docker login` command to authenticate with the registry and provide the necessary credentials.
If none of the above solutions work, please provide more specific details about the command you are running and any additional error messages or output you are encountering, so I can assist you further.

 

[TYFLOOZY]

I've hunted this forum and find items that are close to this.. but some seemingly too old so I can't get them to apply (or I'm misreading them). I have had an issue where I had to pull an installation of Sonarr and re-install it. So, I deleted Sonarr (using the three dots, selected both items to "delete") deleted.

Then go to applications, choose TrueCharts Sonarr, and upon install I receive these messages:

Container image "tccr.io/truecharts/kubectl:v1.26.0@sha256:323ab7aa3e7ce84c024df79d0f364282c1135499298f54be2ade46508a116c4b" already present on machine

Followed by:

Back-off restarting failed container

And then it just fails, sticking in the "Deploying" mode. I've left it sit in deploying overnight and it never rectifies itself. I'm not sure the best way to proceed.

Were you able to fix this? Looking to see if anyone has found solutions to this. I have downloaded filebrowser before, but deleted to reorganize my dataset and getting the same error. I Deleted it multiple times and have deleted/recreated the dataset as well while checking Container Images and saw that it was deleted. I'm curious if one of the solutions above helped as well.

If the only way to make this work is in the shell, please share the specific commands that are needed, thanks!

The Logs aren't showing much as well...

 

[sfatula]

But as sretalla noted above, you need to look at the container logs, not the logs you are showing. The actual problem is most likely in the container log. If you select the app in the list, then in the workload box on the right, bottom right of that box is "view logs"

As it is truecharts, your best bet is always their discord though.

 

[TYFLOOZY]

Whoops, I thought I attached those as well. I'm not too familiar with logs yet on understanding them fully, but I'm guessing it's something to do with permissions with with Data set i created? Also I'm using the TrueNAS app, not TrueCharts.

 

[sfatula]

Yep, permissions issue, sort that out and it will likely work

 

[TYFLOOZY]

Yep, permissions issue, sort that out and it will likely work

Thanks!