docker pull command in Cobia?

[toury]

Some apps could failed to pull image during upgrade in Truenas, it can be fix using `docker pull image ...` to manually pull the image in past.

Since `docker` has been completely removed from os in Cobia, I was wondering if there was any alternative way to pull image manually when `Error: ImagePullBackOff` occur?

Restart the app cannot fix the error, I didn't find similar command in kubectl like k3s kubectl pull image.

2024-01-02 19:58:12
Failed to pull image "tccr.io/tccr/db-wait-postgres:v1.1.0@sha256:a163c7836d7bb436a428f5d55bbba0eb73bcdb9bc202047e2523bbb539c113e6": rpc error: code = NotFound desc = failed to pull and unpack image "tccr.io/tccr/db-wait-postgres@sha256:a163c7836d7bb436a428f5d55bbba0eb73bcdb9bc202047e2523bbb539c113e6": failed to resolve reference "tccr.io/tccr/db-wait-postgres@sha256:a163c7836d7bb436a428f5d55bbba0eb73bcdb9bc202047e2523bbb539c113e6": tccr.io/tccr/db-wait-postgres@sha256:a163c7836d7bb436a428f5d55bbba0eb73bcdb9bc202047e2523bbb539c113e6: not found
2024-01-02 19:58:12
Error: ErrImagePull
2024-01-02 19:58:12
Error: ImagePullBackOff

 

[Bear Tan]

I got the same question as yours.
I try k3s crictl pull image "tccr.io/tccr/nextcloud-fpm:v28.0.1"
But got error：
"pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed".

I am not able to access https://tccr.io by using both my local network (In China...) and VPN (India and Malaysia), but previously I can. Is the tccr.io repository server down or my network has problem?

---

I follow the advise here to refresh TrueCharts and it's fixed.

https://www.truenas.com/community/threads/apps-broke

 

[Perpetual Nomad]

Some apps could failed to pull image during upgrade in Truenas

Same problem, were you able to resolve this?

 

[aekt]

should be

k3s ctr images pull <image_with_tag>

 

[toury]

Same problem, were you able to resolve this?

Just let k3s fix it automatically, since I did not find right command to pull the image. Kubernetes will retry the failed command and fix the error, called self-healing that is k3s will try to pull the failed image after a while. The other possible options is go to apps' deployment config page/settings, click apply without make any changes.

If the ErrImagePull error message was caused by a temporary unstable network connection, it can be fix by repull the image. Otherwise you better to check your network status or Proxy/VPN/DNS settings.