[Success] Image created successfully [Info] Verifying image integrity... [Success] Image passed integrity checks! [Info] Pulling old image for delta generation [==================================================>] 100% [Success] Cached image pulled in 1 second [Info] Generating delta for faster device updates [Success] Delta generated in 2 seconds; size: 496.24 KB [Info] To enable deltas, see https://docs.resin.io/runtime/delta/ [Info] Uploading image to registry... [===============================> ] 62%[Error] Build failed: denied: requested access to the resource is denied
We are just triaging this issue, as it was brought up by our internal tests too. Looks like there’s a potential fix being added soon.
In the meantime can you try to repush? This issue should happen only sporadically (just a few % of the cases in our tests), so a repush should succeed.
Sure, repush did succeed, but I thought it was worth reporting it.
Maybe just changing the error message to ask for a repush would be good enough for a fix ?
Thanks for the report for sure.
Getting the fix out is likely quicker than updating the error message, though. Sorry about the inconvenience.
We’ve seen a sporadic error that could be related to this as well. Has the fix discussed above been implemented?
Part of the log:
... [===============================> ] 62% [===============================> ] 62% [===============================> ] 62%[Error] Build failed: denied: requested access to the resource is denied remote: error: hook declined to update refs/heads/master To firstname.lastname@example.org:project_xyz/xyz.git ! [remote rejected] HEAD -> master (hook declined) error: failed to push some refs to 'email@example.com:project_xyz/xyz.git'
And once again :
[Build] Successfully tagged registry2.resin.io:443/fleetmanagement/d0d0b834016850d270c1742a5279e41158fa45b5:latest [Success] Image created successfully [Info] Verifying image integrity... [Success] Image passed integrity checks! [Info] Uploading image to registry... [=================> ] 34%[Error] Build failed: denied: requested access to the resource is denied
A “repush” fixed the error, soI still think it wouldn’t be a big deal if there was a suggestion message asking to repush (in case defintive fix is not possible).
@Tristan107 We just merged a fix for this error, and it should be merged today or tomorrow. It’s caused by docker requesting access to images that do not belong to the user, to use as a cache for the push. I’ll update this post when the fix is deployed.
Hey @Tristan107 just to let you know, we’ve deployed a fix for this, please do get in touch if you experience the same issue.