-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish various docker image on git-tag #625
Conversation
* Add Package.Dockerfile as flexible build source * Add docker-compose.package.yml as intermediary config * CI will use new github action YAML format it only publish the docker image on git tag * Add debian:latest, debian:slim, and alpine as base image * Add documentation
Signed-off-by: Fahmi Akbar Wildana <f.a.wildana@gmail.com>
Signed-off-by: Fahmi Akbar Wildana <f.a.wildana@gmail.com>
Signed-off-by: Fahmi Akbar Wildana <f.a.wildana@gmail.com>
Signed-off-by: Fahmi Akbar Wildana <f.a.wildana@gmail.com>
Signed-off-by: Fahmi Akbar Wildana <f.a.wildana@gmail.com>
something weird about CircleCI build it can't find target/release/nu although it's whitelisted in the .dockerignore 馃
Status update $ docker run -it nu:glibc-busybox
/bin/nu: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory and $ docker run -it nu:glibc-distroless
/bin/nu: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory still not working when executed directly |
* Add libdl.so.2 for glibc-busybox * Change base-image of glibc-distroless to gcr.io/distroless/cc
$ docker run -it --rm docker.pkg.github.com/drsensor/nushell/nu:glibc-busybox
/bin/nu: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory |
because distroless/cc doesn't contain libz
status update: everything works now |
@DrSensor - great, is there anything I need to do to turn on support for the github action parts so that we can test the CI changes? |
@jonathandturner - for quick testing, you can fork my nushell-fork then try if using another docker registry
-REGISTRY: docker.pkg.github.com/${{ github.repository }}
+REGISTRY: quay.io/nushell-test
...
-env: { REGISTRY: 'docker.pkg.github.com/${{ github.repository }}' }
+env: { REGISTRY: 'quay.io/nushell-test' } |
@DrSensor - might be easier to talk on here rather than discord :) I'm okay with landing this and testing it after it lands. If it doesn't do what you want, we can revert and try again. |
@jonathandturner sounds good to me 馃憤 |
not tested yet, there is a high chance it need to be moved into separate repo this ci config is a ripoff from nushell/nushell#625
not tested yet, there is a high chance it need to be moved into separate repo this ci config is a ripoff from nushell/nushell#625
not tested yet, there is a high chance it need to be moved into separate repo this ci config is a ripoff from nushell/nushell#625
Signed-off-by: nibon7 <nibon7@163.com>
Signed-off-by: nibon7 <nibon7@163.com>
* Fix docs for all commands * ci skip * Refresh docs
About
This PR is about adding CI for publishing docker image on git-tag with various base image. Hopefully, this can make developing plugin a bit easier for certain scenario.
Motivation
Personally I do this to evaluate the new format of github action, test out how to do cross compilation to put them inside docker image for quick manual test, and finally hoping to replace the legacy github action on one of my project 馃構
Actually I want to use nushell in SBC or MiniPC as a lightweight alternative of osquery. I think nushell is a great project 馃憤
Demo
I'm not yet fully check all the image tag but for now you can try it via:
see the available tag in this table