#docker (2022-07)

docker

All things docker

Archive: https://archive.sweetops.com/docker/

2022-07-06

azec avatar

What if any alternatives to Docker Desktop are people using on Mac computers with Apple M1 chips ( darwin/arm64 )?

sheldonh avatar
sheldonh

FYI I just tried kind the other day and it’s my go to right now for quick cli initialization. Don’t remember if minikube has features that kind doesn’t, but worth checking out. go install kind repo and it just worked for me and since it’s go should compile for your platform with no fuss I hope.

azec avatar

I used minikube+hyperkit on the previous Intel-based MacBookPro. Now with switch to M1, I am having hard time finding any minikube driver that works that is also free.

azec avatar

I mean, my company does provide Docker Desktop licenses, but I was so relieved with being able to get everything done just with minikube+hyperkit for about 1yr.

2022-07-13

azec avatar

I have been successfully pulling down geodesic image from DockerHub all morning and now it stopped working.

 => [internal] load build definition from Dockerfile                                                                                                                  0.0s
 => => transferring dockerfile: 37B                                                                                                                                   0.0s
 => [internal] load .dockerignore                                                                                                                                     0.0s
 => => transferring context: 2B                                                                                                                                       0.0s
 => ERROR [internal] load metadata for docker.io/cloudposse/geodesic:latest-debian                                                                                    1.2s
 => [auth] cloudposse/geodesic:pull token for registry-1.docker.io                                                                                                    0.0s
------
 > [internal] load metadata for docker.io/cloudposse/geodesic:latest-debian:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 403 Forbidden
make[1]: *** [docker/build] Error 1
make: *** [build] Error 2

Related issue: https://forums.docker.com/t/failed-to-authorize-rpc-error-code-unknown-desc-failed-to-fetch-oauth-token-unexpected-status-401-unauthorized/118562/40

I have not been able to find any workarounds as of right now, but tried: • Different IPs (via VPN and different ISP connections) • Restarting Docker Desktop • Re-login to Docker Hub with docker login ——————————– Curious if anyone else ran in anything similar in the past?

Failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 401 Unauthorized

I got this working by disabling buildkit. My issue was being behind a firewall, and disabling buildkit made everything good.

2022-07-14

azec avatar

I have now tried to pull down base image explicitly with

$ docker login
Authenticating with existing credentials...
Login Succeeded
$ docker pull cloudposse/geodesic:latest-debian
Error response from daemon: Head "<https://registry-1.docker.io/v2/cloudposse/geodesic/manifests/latest-debian>": unknown: image access restricted: cloudposse/geodesic blocked for organization vznbi

The error above tells me that at some point either: a) someone who can control our org in Docker Hub, has prevented us to access cloudposse/geodesic public image b) someone on the other end has prevented cloudposse/geodesic pulls for our Docker Hub org

I think (a) is more probable than (b) but need to verify…

bradym avatar

For what it’s worth, I was just able to pull it with no issue:

$ docker pull cloudposse/geodesic:latest-debian
latest-debian: Pulling from cloudposse/geodesic
b85a868b505f: Already exists 
27a23929c046: Pull complete 
346372e5e1e1: Pull complete 
e67973a72171: Pull complete 
4dd45b90da3b: Pull complete 
933d9a84e2a1: Pull complete 
193736eded2f: Pull complete 
0b26a49d7473: Pull complete 
60124c1ce1b2: Pull complete 
8c5c0a1925b3: Pull complete 
1291d455bb6c: Pull complete 
247aa5730bf6: Pull complete 
e5f3e0529290: Pull complete 
4f4fb700ef54: Pull complete 
f62f155b9ff8: Pull complete 
d053d8d4f385: Pull complete 
34d55f4a2ff5: Pull complete 
a15bede002f9: Pull complete 
c9fac60eb0d9: Pull complete 
ae3024fd06d3: Pull complete 
759f98df0dbf: Pull complete 
7e49a5f1dfbb: Pull complete 
4b72ee9f0674: Pull complete 
df48fa425ddd: Pull complete 
f6e6cad62102: Pull complete 
2b82fc1b468e: Pull complete 
fff9caede657: Pull complete 
435d3cf072f8: Pull complete 
37dfb3c581de: Pull complete 
e3ac50cc8097: Pull complete 
3196bb658e9d: Pull complete 
Digest: sha256:bd04298beb5307bf7d375b2b3ec021e5b7109bc5905cc6eab2a7cadd14044d3a
Status: Downloaded newer image for cloudposse/geodesic:latest-debian
docker.io/cloudposse/geodesic:latest-debian
azec avatar

Turns out our org only allows Official Docker Images in Docker Hub, so when I login with docker CLI, that image gets blocked. Solved with docker logout

2022-07-15

    keyboard_arrow_up