Created
July 21, 2018 04:11
-
-
Save inevity/90bfce7063184b5fb2cd23ba61a93ac9 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## use the in-k8s register | |
``` | |
make push | |
kc get pod | |
metallb-system controller-76bfc5b8f-gn67m 1/1 Running 0 7m 172.17.0.6 minikube | |
metallb-system controller-7cbddf6c7-75rr2 0/1 ImagePullBackOff 0 1m 172.17.0.4 minikube | |
metallb-system speaker-2n5vj 0/1 ImagePullBackOff 0 1m 10.0.2.15 minikube | |
metallb-system test-bgp-router-5d5b7ffdb7-skgqg 0/1 ImagePullBackOff 0 1m 172.17.0.7 minikube | |
metallb-system test-bgp-router-fd8d857bd-4fmw8 1/1 Running 0 7m 172.17.0.5 minikube | |
kc describe pod speaker-2n5vj -n metallb-system | |
Events: | |
Type Reason Age From Message | |
---- ------ ---- ---- ------- | |
Normal SuccessfulMountVolume 1m kubelet, minikube MountVolume.SetUp succeeded for volume "speaker-token-m4pg5" | |
Warning Failed 1m kubelet, minikube Failed to pull image "10.103.73.236:80/speaker:1532145540.N-amd64": rpc error: code = Unknown desc = Error response from daemon: Get http://10.103.73.236:80/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers) | |
Warning Failed 1m kubelet, minikube Error: ErrImagePull | |
Normal BackOff 1m kubelet, minikube Back-off pulling image "10.103.73.236:80/speaker:1532145540.N-amd64" | |
Warning Failed 1m kubelet, minikube Error: ImagePullBackOff | |
Normal Pulling 47s (x2 over 1m) kubelet, minikube pulling image "10.103.73.236:80/speaker:1532145540.N-amd64" | |
``` | |
## use the local registry same as above | |
## use the dock pub registry | |
only spkear and controller can start,but test-bgp-route fail. | |
I first delete origin iamge by delete -f yaml ,then apply. | |
Then If make push finished. i manual run apply -f manifests/test-bgp-router.yaml. Then all ok | |
I dont why ? | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In-k8s,no_proxy issue