-
I'm trying to ascertain whether the behaviour I've ran into is user error on my part or a bug within Talos. The Talos installation ISO fails to pull the installation image if a TLS secured pull through registry is specified. The error is as follows.
The docker registry is properly set up and certs are valid.
This error persists when setting the insecureSkipVerify parameter in a RegistryTLSConfig for ghcr.io. Is this error unrelated to the TLS server certificate verification that's disabled by that flag? Using self signed registry server and client certiciates gave the same error as using one signed by my internal CA. Again it is set up just fine on the registry side of things, confirming it is a Talos issue.
Additionally the documentation examples show the key and crt paramaters of clientIdentity as being doubly base64 encoded. I do not understand why this would be the case if it's being encoded and decoded once. How would I go about inspecting the containerd registry hosts configuration located at I have included a dump of the VM's dmesg when attempting to perform the installation The following commands were performed to generate the registry and client keys.
Any insights or obvious things I have overlooked? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
could you provide the machine config used ? |
Beta Was this translation helpful? Give feedback.
could you provide the machine config used ?