Open abh opened 7 years ago
In case someone else runs into the same, logging in as the core user with docker login quay.io
and then pull'ing the images manually fixed it. I only needed 3 images; everything else got pulled correctly..
Ugh, I think I mixed up the base64 encoding when I recreated the correct pull secret.
Feature request: It'd be nice if kubectl could create a pull secret (or the docs told how to) from the pull-secret.json file. It doesn't support creating one without an email address, so it has to be "manually" encoded and setup.
It'd be nice if kubectl could create a pull secret (or the docs told how to) from the pull-secret.json file.
This is pretty easy to do:
kubectl create secret generic coreos-pull-secret --from-file=".dockerconfigjson= pull-secret.json" --type='kubernetes.io/dockerconfigjson'
But yes I agree that is should be documented somewhere. We'll work on that.
Doesn't work for me. I am getting error:
kubectl create secret generic coreos-pull-secret --from-file=".dockerconfigjson= config.json" --type='kubernetes.io/dockerconfigjson' -n spinnaker
error: error reading config.json: no such file or directory
Hi , i am not able to pull any images from any of the repository from tectonic console ("imagepullbackoff error") , see this is my
deployment.yml file apiVersion: extensions/v1beta1 kind: Deployment metadata: name: simple-deployment namespace: default labels: k8s-app: simple spec: replicas: 3 revisionHistoryLimit: 2 strategy: type: RollingUpdate rollingUpdate: maxUnavailable: 0 maxSurge: 1 template: metadata: labels: k8s-app: simple spec: containers:
Issue Report Template
Tectonic Version
1.7.1
Environment
bare metal
Expected Behavior
Pod starting
Actual Behavior
All the other pods started okay. I checked that the coreos-pull-secret matches what I download from the tectonic account. (It didn't at first; so I updated it after the kube API was up).