forked from percona/postgres_exporter
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4 from quintoandar/fix-dockerfile
chore: fix dockerfile
- Loading branch information
Showing
1 changed file
with
7 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,15 +3,16 @@ FROM golang:1.19-alpine as build | |
WORKDIR ${GOPATH}/src/github.com/quintoandar | ||
RUN apk update && apk add make git curl && git clone --branch main https://github.com/quintoandar/postgres_exporter.git | ||
WORKDIR ${GOPATH}/src/github.com/quintoandar/postgres_exporter | ||
ENV GOARCH=amd64 | ||
RUN make release | ||
RUN chmod +x postgres_exporter && mv postgres_exporter /tmp/postgres_exporter | ||
|
||
|
||
FROM quay.io/prometheus/busybox:latest as final | ||
LABEL maintainer="The Prometheus Authors <[email protected]>" | ||
|
||
COPY --from=build ["/tmp/postgres_exporter", "/bin/postgres_exporter" ] | ||
COPY --from=build ["/tmp/postgres_exporter", "/" ] | ||
|
||
WORKDIR /opt/exporter | ||
|
||
EXPOSE 9187 | ||
|
||
EXPOSE 9187 | ||
USER nobody | ||
ENTRYPOINT [ "/bin/postgres_exporter" ] | ||
ENTRYPOINT [ "/postgres_exporter" ] |
85a52b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @eliasscosta!
The GitLeaks SecTool reported some possibly exposed credentials/secrets, how about giving them a look?
GitLeaks Alert Async
In cases of false-positives, more information is available on GitLeaks FAQ
If you had any other problem or question during this process, be sure to contact us on the #security channel on Slack at the @team-appsec group!