Larry Brigman

I got the same message while launching a docker container. After that the playbook to that node would never complete getting a different error. failed: [10.109.180.169] (item=docker-registry-default.gsm-test.lab.c-cor.com/gsm/memcached:1.6) => {"changed": false,...

Almost two years on. No solution? We are hitting this in our testing trying to test our deployment for offline/isolated environments. We have control_plane_ee_image set correctly in the AWX deployment...

We got it figured out. Here are the details for others to follow without needing to fully dig into all the details though; YMMY depending on versions. Need to create...

I did notice a project that is working with MicroShift in Docker - https://github.com/christianh814/fauxpenshift

I had an open issue like this too. There are two different things here. package naming and meta data. package naming is a convention and you must handle that manually....

I'm installing on Rocky 9 without issue with Kubekey versions v3.0.13 and v3.1.0-alpha-7 There is a limited number of Kubernetes releases that will install with v3.0.13 We were only able...

The location being referenced may be due to using kk init os with the -a artifact.tgz However, the artifact file didn't have any ISO images within it.

For some reason, I had thought I had seen the details in the standard config file for installing. If that is not the case then this can be closed.

close issues. Works as documented.

containerd does support insecure registries. The configuration is harder to find as it has changed. The recommendation is to move to using: [plugins."io.containerd.grpc.v1.cri".registry] config_path = "/etc/containerd/certs.d" Now with this configuration...