-
I'm attempting to use the embedded registry in an air-gapped environment with just a single server node and agent to start with. I've followed the air gap documentation and all images that I need are scp'ed over to the server node where I import them. The server node starts up fine, pods are created using the containers I've imported, and all looks normal on the command line with When I install the agent on another machine, k3s starts up but the pods are stuck in
On the agent machine, I see these types of errors in syslog:
My
I'm open to any suggestions to debug or clues as to what might be going on. k3s version v1.29.1+k3s2 (57482a1) Node(s) CPU architecture, OS, and Version: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
Where did you put the images? Did you place the archives in the images dir so that they are automatically imported on startup, or did you manually import them? If you manually imported them, did you import them into the correct namespace? Can you show the output of Can you confirm that the embedded registry ports (5001 and 6443) are open between both nodes? |
Beta Was this translation helpful? Give feedback.
-
Right now our process is that an internet connected machine fetches them directly from the registries noted above -- Server node (nuc1):
Agent node (nuc2):
Ports are open - similar output on nuc1. The NUCs are vanilla Ubuntu Server 20.04 installs.
I wasn't aware I could place the images in a directory and they would be imported on startup. I could try that out if you think behavior might be different? |
Beta Was this translation helpful? Give feedback.
-
I ran
I uninstalled both nodes and ran through the install process again putting the image files in |
Beta Was this translation helpful? Give feedback.
Are you sure that you also populated registries.yaml on nuc1? The log output suggests that you have not.