-
Notifications
You must be signed in to change notification settings - Fork 119
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
Question: apko should be support copy files? #852
Comments
the current approach to package them into apk package like this i think https://github.com/wolfi-dev/os/blob/main/container-entrypoint.yaml |
thanks @tuananh. I understand that apko should not be able to exec anything in the build that could variate, because this could be against to reproducible and declarative nature. |
Having support to copy files (which can be anything from binaries, config file, execution code, etc) If apko whats to be better than Dockerfile ... then I'd suggest have either apko or melange support COPY files/folder funtionality |
Yes, you can copy files into an apk with melange. It’s already supported. |
Just to clarify on this issue. Apko doesn't support copy files and seems to be is the architecture design If you want to use the copy file function in melange here is a basic example Imagine you have a file called Example of melange pipeline section pipeline:
- runs: |
BUILD_DIR="/home/build"
cp "${BUILD_DIR}/mycode.sh" "${{targets.destdir}}/mycode.sh"
...
... Hope that helps to everyone who read this post |
i have an example (template) here how to package file with melange and then use that package in apko. |
apko have the chance to copy some files? or execute something?
apko is great to gen base images, but is common require that this bases images need some configuration file or script and they are copied in base image in order to abstrac final application images (or images uses for build). Does it make sense? Or we should make this inside of a build system?
The text was updated successfully, but these errors were encountered: