You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works well BUT in alpine old package files are apparently quickly deleted when not referenced by the index anymore. That makes our builds often fail even only a few hours/days after the last update.
To work around this, we tried to use a pull through cache:
In our first tries, we hard-coded our credentials into the repositories URLs in the apko.yaml file.
We got this error:
Error: failed to get package list for image: error getting package dependencies: error getting repository indexes: no key found to verify signature for keyfile [email protected]; tried all other keys as well
2024/05/28 14:25:08 error during command execution: failed to get package list for image: error getting package dependencies: error getting repository indexes: no key found to verify signature for keyfile [email protected]; tried all other keys as well
I assume the logic that automagically loads the correct keys for the standard URLs doesn't trigger here?
Anyways, we can then add the keyring files individually:
Error: failed to get package list for image: error getting package dependencies: error getting repository indexes: no key found to verify signature for keyfile [email protected]; tried all other keys as well
2024/05/28 14:26:58 error during command execution: failed to get package list for image: error getting package dependencies: error getting repository indexes: no key found to verify signature for keyfile [email protected]; tried all other keys as well
The text was updated successfully, but these errors were encountered:
Context:
Sample apko.yaml:
This works well BUT in alpine old package files are apparently quickly deleted when not referenced by the index anymore. That makes our builds often fail even only a few hours/days after the last update.
To work around this, we tried to use a pull through cache:
https://jfrog.com/help/r/jfrog-artifactory-documentation/alpine-linux-repositories
In our first tries, we hard-coded our credentials into the repositories URLs in the apko.yaml file.
We got this error:
I assume the logic that automagically loads the correct keys for the standard URLs doesn't trigger here?
Anyways, we can then add the keyring files individually:
But it doesn't work for all keys?
The text was updated successfully, but these errors were encountered: