Skip to content

Dockerfile: Avoid LegacyKeyValueFormat warning#1231

Merged
mergify[bot] merged 1 commit into
ceph:masterfrom
anoopcs9:fix-dockerfile-warning
Feb 12, 2026
Merged

Dockerfile: Avoid LegacyKeyValueFormat warning#1231
mergify[bot] merged 1 commit into
ceph:masterfrom
anoopcs9:fix-dockerfile-warning

Conversation

@anoopcs9

@anoopcs9 anoopcs9 commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator 
1 warning found (use docker --debug to expand):
  - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 49)

@anoopcs9
Dockerfile: Avoid LegacyKeyValueFormat warning
32b33db 
1 warning found (use docker --debug to expand):
  - LegacyKeyValueFormat: "ENV key=value" should be used instead of
    legacy "ENV key value" format (line 49)

Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
@anoopcs9 anoopcs9 added the no-API This PR does not include any changes to the public API of a go-ceph package label Feb 12, 2026
@mergify mergify Bot added the queued label Feb 12, 2026
@mergify mergify Bot merged commit a9b21e2 into ceph:master Feb 12, 2026
25 of 28 checks passed
@mergify

mergify Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

Rule: default

  • ✅ Entered queue — 2026-02-12 15:43 UTC
  • ✅ Checks passed · in-place
  • ✅ Merged — 2026-02-12 15:43 UTC · at 32b33dba2123a172744b31fd6c31efed317e7ccf

This pull request spent 6 seconds in the queue, with no time running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = check
    • check-neutral = check
    • check-skipped = check
  • any of [🛡 GitHub branch protection]:
    • check-success = test-suite (pacific)
    • check-neutral = test-suite (pacific)
    • check-skipped = test-suite (pacific)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-suite (quincy)
    • check-neutral = test-suite (quincy)
    • check-skipped = test-suite (quincy)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-suite (reef)
    • check-neutral = test-suite (reef)
    • check-skipped = test-suite (reef)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-suite (squid)
    • check-neutral = test-suite (squid)
    • check-skipped = test-suite (squid)

@mergify mergify Bot removed the queued label Feb 12, 2026
@phlogistonjohn

phlogistonjohn commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator

There's no reef tag at https://quay.ceph.io/repository/ceph-ci/ceph any more.
Rather than argue with the ceph folks shall we just remove pre-reef? Reef is in a funny state of being both EOL and not EOL on the Ceph end.

@phlogistonjohn

phlogistonjohn commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator

Oh. pre-reef is not required for mergify - my bad. But we're probably going to see other pre-reef runs fail FWIW.

@anoopcs9 anoopcs9 deleted the fix-dockerfile-warning branch February 12, 2026 16:11
@anoopcs9

anoopcs9 commented Feb 12, 2026

Copy link
Copy Markdown
Collaborator Author

There's no reef tag at https://quay.ceph.io/repository/ceph-ci/ceph any more. Rather than argue with the ceph folks shall we just remove pre-reef? Reef is in a funny state of being both EOL and not EOL on the Ceph end.

We were in a similar situation about two months ago, and it eventually got resolved (I had started this thread, but it got stalled again).

Oh. pre-reef is not required for mergify - my bad. But we're probably going to see other pre-reef runs fail FWIW.

Let's wait and see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@phlogistonjohn phlogistonjohn phlogistonjohn approved these changes

@ansiwen ansiwen Awaiting requested review from ansiwen

Assignees

No one assigned

Labels

no-API This PR does not include any changes to the public API of a go-ceph package

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@anoopcs9 @phlogistonjohn