-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk #4165
Comments
From the logs it seems you didn't run the After downloading the new release, please use the following steps, to start from a clean environment:
and the error about |
Hi anjannath, thank you for the response. I deleted the crc instance as you suggested and re-downloaded all the files for version 2.36.0 - now it seems to work. I'm sure that I tested with 2.36.0, but maybe I was missing the "-f" flag when deleting the crc instance ¯_(ツ)_/¯ What was the issue here? I'd like to be able to understand it so I can troubleshoot it next time. Anyways, you can close this ticket IMO. Thank you for the fast response. Kind regards, |
#4110 have all the details. |
I'm trying to get CRC 2.34.1 working on my local machine, but it fails with
Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk
. I also tested with the latest CRC release (2.36.0 at the time of writing).I followed the installation instructions and used
sudo apt-get update && sudo apt install -y qemu-kvm libvirt-daemon libvirt-daemon-system network-manager
to install the prerequisites. My user is part of the libvirt group etc.I then proceeded with these commands to get crc up and running:
After it failed, I used SSH to connect to the instance and found this:
I tried to fix this with
sudo systemctl restart libvirtd
on my local machine, but without success.I attached the
~/.crc/crc.log
file.crc.log
Any ideas on how to resolve this? I'd really like to use CRC for my local development and testing, since we use OCP 4 at work and I want to evaluate if our local developers could use it.
KInd regards,
Oliver
The text was updated successfully, but these errors were encountered: