IndhumithaR

Hi @phillebaba, As Badal said we did a workaround by creating one hosts.toml file and adding client flag within the host configuration. Here is the sample Hosts.toml for your information,...

Yes, I think it should work. We can try this approach.

> @badaldavda8 @IndhumithaR > > I have created #424 that should resolve this issue. > > For clarification of the change it adds a new flag `--append-mirrors` which when enabled...

Hi @phillebaba, We tried using v0.0.21 and ```--append-mirrors``` set to true. Even then we noticed that the existing hosts.toml which we have is pushed to ```/etc/containerd/certs.d/_backup``` and a new hosts.toml...

Hi @phillebaba We see that the hosts.toml is getting overwritten. It is not getting merged.

> That is the expected behavior. It is not really possible to not backup all of the mirror configuration. We need the original registries to be able to update the...

Hi @phillebaba, We tried disabling spegel mirror configuration. Now we are able to pull docker images but getting the below error often and after multiple retries the image is getting...

Hi @phillebaba, We deployed a pod to pull a docker image, a new node is created and tried to pull the image. After several tries, finally the image is pulled...

@phillebaba, Thanks for you response. This is the hosts.toml, we are currently using. ``` server = 'https://artifact.xxx.com' client = [['/etc/certs/artifact.xxx.com/client.cert','/etc/certs/artifact.xxx.com/client.pem']] [host] [host.'http://10.190.63.87:30020'] capabilities = ['pull', 'resolve'] [host.'http://10.190.63.87:30021'] capabilities = ['pull',...

Hi @phillebaba For the previous question regarding the daemonset, we will create a new issue. But for testing purpose, we tried assigning pods to the nodes in which spegel is...