-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
Official Docker Image #143
Comments
I used `scc` to generate the statistics. I also asked for an official Docker image in boyter/scc#143 so that we might be able to automatically generate the statistics in the future every time something is merged to master. Should be easy with GitHub actions.
I used `scc` to generate the statistics. I also asked for an official Docker image in boyter/scc#143 so that we might be able to automatically generate the statistics in the future every time something is merged to master. Should be easy with GitHub actions.
Yep a docker image sounds like a good idea. I will have a look to see what this involves. |
Based on the work of gitlab-ci-utils/docker-scc (MIT License), I came up with this: # hadolint ignore=DL3007
FROM golang:latest as scc-get
ENV GOOS=linux \
GOARCH=amd64 \
CGO_ENABLED=0
ARG VERSION=v3.0.0
RUN git clone --branch $VERSION --depth 1 https://github.com/boyter/scc
WORKDIR /go/scc
RUN go build -ldflags="-s -w"
FROM scratch
COPY --from=scc-get /go/scc/scc /scc
ENTRYPOINT ["/scc"] which is basically an empty docker image with only the I guess the majority of the work that needs to be doen for this issue is setting up all of the right GitHub Action, correct? |
That would be it as far as I can see. I really need to block out some time to get all of this done. |
Would it be possible that we get an official Docker image? You could host it on GitHub like the pre-compiled binaries. Having a Docker image would simplify the usage with automation (e.g. CI).
The text was updated successfully, but these errors were encountered: