This message was deleted.
# kubernetes
a
This message was deleted.
w
The flow is: 401 unauthorized 200 Get fresh temp token 403 HEAD Access the repo (without the proper token from the registry).
The token in the registry would have worked since I have tested it with a direct v2 request
Copy code
}wolves-2-3:~ # curl -k -H "Accept: application/json"    -H "Authorization: Bearer $token"  <https://pfxm.artiactory.cec.lab.emc.com:443/v2/pfxm-docker-dev/test-container/printheaders/manifests/0.0.1-11>
{
  "schemaVersion" : 1,
  "name" : "test-container/printheaders",
  "tag" : "0.0.1-11",
  "architecture" : "amd64",
So my understanding that doing ctr -a /run/k3s/containerd/containerd.sock images pull does not go through the conf file settings, Also image pull after helm install fails.
• using ctr is not the same as what happen when called from a pod. • It does work when I use username and password. • I still need it to work with a token instead.