Using docker container from quay.io

[kiwiroy]

Using the prebuilt container seems like a good idea in terms of efficiency and simplicity of the yaml definition. Are there any drawbacks?

[vsoch]

Have you tested this? Typically a container with Singularity has permissions or other issues because we aren’t running it privileged, hence the strategy here to install natively.

[kiwiroy]

Have you tested this?

yes, but only with simple command line applications, including this one now.

$ export GITHUB_TOKEN=...
$ curl -L -H "Authorization: token $GITHUB_TOKEN" \
    https://api.github.com/repos/kiwiroy/github-ci/actions/artifacts/18516234/zip > container.zip
$ unzip container.zip
$ singularity run container.sif 
Hold me closer... tiny container :D

[vsoch]

I like this approach, and I have a proposal for you - I do think this approach would work for simple builds, but there is likely to be some issue depending on the build. What do you think about creating a separate workflow - called .github/workflows/container.yml (or something intuitive like that) and then providing this option? Then in the README, clearly state that go.yml is intended to show a native install, and container.yml uses a pre-built container on quay.io. Then the user can select whichever recipe is best fit for their use case.

[kiwiroy]

Sounds good.

• Augment this PR create new file rather than edit.
• Rename original go.yml to native.yml for clarity?
• Update README

[vsoch]

+1 to make the go.yaml more clearly named! I would even go further and call it native-install.yml.

[vsoch]

Beautiful! Are you finished up @kiwiroy and this is ready for merge?

[kiwiroy]

Thanks. I'd consider it ready for merging.

[vsoch]

Thank you @kiwiroy ! I think this greatly improves the repository with the additional example.