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
the docker images created will have the following content in the /etc/apk/repositories file
@local ./packages
https://packages.wolfi.dev/os
This will cause the apk add command to fail when a user wants to add packages outside apko/melange (e.g using the image produced from APKO as FROM in a Dockerfile and executing apk commands).
/ # apk add curl
WARNING: opening ./packages: No such file or directory
WARNING: The repository tag for world dependency 'mypackage@local' does not exist
ERROR: Not committing changes due to missing repository tags. Use --force-broken-world to override.
Is this supposed to be like this or can we avoid to add local repositories in the /etc/apk/repositories file? Or, is there a way to exclude repositories programmatically?
The text was updated successfully, but these errors were encountered:
When building packages with melange and using these in apko by referencing a repository that points to a local folder like this:
the docker images created will have the following content in the
/etc/apk/repositories
fileThis will cause the
apk add
command to fail when a user wants to add packages outside apko/melange (e.g using the image produced from APKO as FROM in a Dockerfile and executing apk commands).Is this supposed to be like this or can we avoid to add local repositories in the
/etc/apk/repositories
file? Or, is there a way to exclude repositories programmatically?The text was updated successfully, but these errors were encountered: