Skip to content

Commit

Permalink
Bump library/debian (#12)
Browse files Browse the repository at this point in the history 
Bumps library/debian from bookworm-20240812-slim to bookworm-20240904-slim.

---
updated-dependencies:
- dependency-name: library/debian
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
  • Loading branch information
@dependabot
dependabot[bot] authored Sep 15, 2024
1 parent dc4e351 commit 33ffb79
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Dockerfile
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM docker.io/library/debian:bookworm-20240812-slim
FROM docker.io/library/debian:bookworm-20240904-slim

ENV DEBIAN_FRONTEND noninteractive

Check warning on line 3 in Dockerfile

View workflow job for this annotation

GitHub Actions / build / build

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 3 in Dockerfile

View workflow job for this annotation

GitHub Actions / build / build

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 3 in Dockerfile

View workflow job for this annotation

GitHub Actions / build / build

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/

Expand Down

0 comments on commit 33ffb79

Please sign in to comment.