Skip to content

Commit

Permalink
updated Blackfire to 2.28.22
Browse files Browse the repository at this point in the history
  • Loading branch information
blackfire-tortue-geniale committed Jan 7, 2025
1 parent b1daa70 commit 3519383
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
FROM alpine:3.20 AS bin
FROM alpine:3.21 AS bin

ARG TARGETARCH

ADD https://packages.blackfire.io/binaries/blackfire/2.28.21/blackfire-linux_${TARGETARCH:-amd64} /usr/local/bin/blackfire
ADD https://packages.blackfire.io/binaries/blackfire/2.28.22/blackfire-linux_${TARGETARCH:-amd64} /usr/local/bin/blackfire
RUN chmod 0555 /usr/local/bin/blackfire

FROM alpine:3.20
FROM alpine:3.21

ENV BLACKFIRE_CONFIG /dev/null

Check warning on line 10 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 10 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV BLACKFIRE_LOG_LEVEL 1

Check warning on line 11 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 11 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV BLACKFIRE_SOCKET tcp://0.0.0.0:8307

Check warning on line 12 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 12 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
EXPOSE 8307

RUN apk add --no-cache curl socat \
RUN apk add --no-cache curl socat ca-certificates \
&& addgroup -S blackfire \
&& adduser -S -H -G blackfire -u 999 blackfire

Expand Down

0 comments on commit 3519383

Please sign in to comment.