5.1 step 6 getting "error: unable to upgrade connection: container not found ("simpleapp")"
Hello,
On 5.1, I'm getting stuck after trying to follow step 6. When I try to run kubectl exec -c simpleapp -it try1-5db9bc6f85-whxbf \-- /bin/bash -c'echo $ilike'
I get this error error: unable to upgrade connection: container not found ("simpleapp")
When I run kubectl get pods
all 6 of my try1 pods have the status of ImagePullBackOff
.
How do I resolve this issue? Thanks in advance
Answers
-
Hi @quachout,
When describing either one of the six
try1
pods, what events are displayed at the bottom of the output?Have the earlier issues from chapters 2 and 3 been fixed? Is the container runtime operational on both nodes? Is the private repository operational? Is access to the private repository properly configured on both nodes? Is the desired "simpleapp" container image in the repository?
Regards,
-Chris0 -
@chrispokorni This is what is displayed after describing one of the
try1
pods:Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 84s default-scheduler Successfully assigned default/try1-69c9f5ff6b-2fn98 to ip-172-31-5-77 Normal Pulled 83s kubelet Container image "registry.k8s.io/goproxy:0.1" already present on machine Normal Created 83s kubelet Created container goproxy Normal Started 82s kubelet Started container goproxy Normal Pulling 35s (x3 over 83s) kubelet Pulling image "10.97.40.62:5000/simpleapp" Warning Failed 35s (x3 over 83s) kubelet Failed to pull image "10.97.40.62:5000/simpleapp": rpc error: code = NotFound desc = failed to pull and unpack image "10.97.40.62:5000/simpleapp:latest": failed to resolve reference "10.97.40.62:5000/simpleapp:latest": 10.97.40.62:5000/simpleapp:latest: not found Warning Failed 35s (x3 over 83s) kubelet Error: ErrImagePull Normal BackOff 8s (x6 over 82s) kubelet Back-off pulling image "10.97.40.62:5000/simpleapp" Warning Failed 8s (x6 over 82s) kubelet Error: ImagePullBackOff
Yes the earlier issues from ch2 and 3 have been fixed.
When I runsudo systemctl status docker
to check if the container runtime is operational I get this errorUnit docker.service could not be found
.I wasn't getting this error before when I ran
kubectl get pods
all of the try1 pods were Running but for some reason starting yesterday, my pods are in the ImagePullBackOff status. Is this a problem with the simpleapp server from the Linux Foundation?0 -
Hi @quachout,
If all installation and config steps were closely followed, then Docker should not be your runtime. We are using Containerd instead, as mentioned in my earlier responses to you as well.
The Linux Foundation does not run or own a "simpleapp" server.
The "simpleapp" container image is built by the learner/you in Lab 3, stored in a private repository - also built by the learner/you in your own Kubernetes cluster. This "simpleapp" container image will eventually be pulled by your container runtime (Containerd, not Docker) as requested by the Kubernetes framework on behalf of the try1 Deployment.The failures listed in the Events may be caused either by an empty local repository if the "simpleapp" container image was not successfully pushed in the local repo, or a misconfiguration of the Containerd container runtime to access the local repo.
From both nodes, you can check the repo catalog with:
curl $repo/v2/_catalog
The command should return an empty repository if no images are stored, or "simpleapp" if the image was successfully pushed in the repo.
Regards,
-Chris0 -
When I run
curl $repo/v2/_catalog
on both nodes I get:curl: (3) URL using bad/illegal format or missing URL
What should I do to get "simpleapp" to be successfully pushed to the repo again?
0 -
@chrispokorni oh wait I remembered that I wasn't able to use $repo so instead I typed out the entire IP. So instead of using
curl $repo/v2/_catalog
I'm usingcurl 10.97.40.62:5000/v2/_catalog
and this returned and empty repository{"repositories":[]}
What should I do to get "simpleapp" to be successfully pushed to the repo again?
0 -
@chrispokorni when I tried to follow the steps again in Lab 3. I'm now running into this issue of
The connection to the server 172.31.5.77:6443 was refused - did you specify the right host or port?
when I run
kubectl get nodes
0 -
Hi @quachout,
Isn't this the earlier reported issue that was eventually fixed, from another discussion thread?
Regards,
-Chris0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 158 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 236 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 61 All In Program
- 61 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)