[image] OCI from hub.docker.com getting unable to retrieve auth token: invalid username/password: authentication required. Creating a fresh topic for that failure. For debugging reasons I would like to see the content the authfile that is provided to skopeo. Which path should be travelled to…

For what it is worth: I do have valid credentials. Example given: $ skopeo inspect docker://dhi.io/harbor-portal:2-debian-dev | jq .Name "dhi.io/harbor-portal" $

A single thread for the same problem is enough. run as root and see if the same works. EDIT: to be clear, that wasn’t a complaint — easier for me to follow one thread on the same failure, that’s all.

Travelled path, for me a long walk, you are welcome to speed run it. a dry-run: $ skopeo-trap yeah what ever ever --authfile=/etc/hosts so far $ cat /dev/shm/af_data -rw-r--r-- 1 root root 908 16 aug 11:50 /etc/hosts $ head -n 1 /dev/shm/af_content 127.0.0.1 localhost $ What is inside skopeo-tr…

Does this mean in tools like “incus” or “incus-compose” we should base64 the result?

For what it is worth: an actual bugreport is pending.

Bugreport created: [image] Allow @ in password for OCI registries Consider this topic a bugreport. If there are better places for such reports, please say so.

Content of skopeo authfile

Incus

stappers (Geert Stappers) August 27, 2026, 12:52pm 7

Bugreport created: