-
Notifications
You must be signed in to change notification settings - Fork 239
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
[BUG] - Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk (x31) #4156
Comments
This looks like dup to #4110 and can you try #4110 (comment) workaround? |
@praveenkumar
|
@aolloh did you try the latest version of |
@praveenkumar Yes, I had a same error with the latest version
|
@aolloh I didn't notice that you are using nested virtualization, any reason you are not able to use your host system instead having a RHEL VM in virtualbox and then using crc? We don't test the nested virt setup.
|
@praveenkumar I wanted to test it in a seperate environment (VM) |
@aolloh As I said we don't have any test in place for nested virt stuff so there might be many reason it fails like IO/CPU/memory resources, and it is hard to debug. I would suggest you to use the host instead of separate VM for crc and see if that works. |
@praveenkumar it works on host. Thanks |
General information
crc setup
before starting it (Yes/No)? yesCRC version
CRC status
$ crc status --log-level debug DEBU CRC version: 2.35.0+3956e8 DEBU OpenShift version: 4.15.10 DEBU Podman version: 4.4.4 DEBU Running 'crc status' CRC VM: Running OpenShift: Unreachable (v4.15.10) RAM Usage: 5.205GB of 12.54GB Disk Usage: 19.81GB of 32.68GB (Inside the CRC VM) Cache Usage: 27.27GB Cache Directory: /home/student/.crc/cache
CRC config
$ crc config view - consent-telemetry : yes
Host Operating System
CRC Setup
Error
The text was updated successfully, but these errors were encountered: