chore(docker): deprecate legacy conf/Dockerfile + conf/docker-compose.yaml (SEC-F25)#435
Merged
Merged
Conversation
….yaml (SEC-F25) The conf/ Docker setup was superseded by juniper-deploy: conf/docker-compose.yaml published all interfaces (8050:8050), set no bind attestation, and still wired a dead cascor-backend:8000 service. juniper-deploy builds the repo-root Dockerfile (python src/main.py, settings-driven, guard-authoritative) and orchestrates the full stack. Remove both legacy files and repoint every live reference. Removed: - conf/Dockerfile (CMD uvicorn main:app --host 0.0.0.0 -- the SEC-F25 latent bypass) - conf/docker-compose.yaml Updated live references (archival notes/ under history/pull_requests/analysis/ development are CI-excluded and left as historical record): - src/tests/regression/test_docker_demo_mode_default.py: drop the conf/Dockerfile demo-mode + existence checks; the root-Dockerfile guards remain (2 tests pass) - .dockerignore, AGENTS.md (2 Docker blocks), docs/DEVELOPER_CHEATSHEET.md, docs/deployment/KUBERNETES_DEPLOYMENT_PLAN.md, notes/juniper-canopy_OTHER_DEPENDENCIES.md, .github/instructions/copilot-instructions.md pre-commit clean (markdownlint + doc-links + flake8 + black/isort). See juniper-ml notes/JUNIPER_2026-07-06_JUNIPER-ECOSYSTEM_LAUNCH-PATH-BIND-AUDIT.md (SEC-F25). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LX5ToumBaABH3QutQC86sM
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Launch-path bind audit SEC-F25 (reclassified). The
conf/Dockerfile(CMDuvicorn main:app --host 0.0.0.0) was a latent guard-bypass, but investigation showed it's paired with a legacy/supersededconf/docker-compose.yaml: it publishes all interfaces (8050:8050), sets no bind attestation, and still wires a deadcascor-backend:8000service. The maintained path isjuniper-deploy, which builds the repo-rootDockerfile(python src/main.py— settings-driven, SEC-F22 guard-authoritative). Per the owner decision, deprecate rather than modernize.Removed
conf/Dockerfileconf/docker-compose.yamlLive references repointed to the root Dockerfile / juniper-deploy
src/tests/regression/test_docker_demo_mode_default.py— drop theconf/Dockerfiledemo-mode + existence checks; the root-Dockerfile demo-mode guard and the path-resolution sanity check remain (2 tests, both pass).dockerignore(stale entry removed)AGENTS.md(both Docker blocks; the "canonical entrypoint" note now readspython src/main.py)docs/DEVELOPER_CHEATSHEET.md(Docker rows + the "add a dependency" step)docs/deployment/KUBERNETES_DEPLOYMENT_PLAN.md(buildfile:+ location)notes/juniper-canopy_OTHER_DEPENDENCIES.md.github/instructions/copilot-instructions.md(conf/ paths)Archival
notes/underhistory/,pull_requests/,analysis/,development/are CI-excluded and intentionally left as historical record.Testing
test_docker_demo_mode_default.py: 2 passed (root-Dockerfile coverage intact).pre-commiton all changed files: markdownlint, doc-links, flake8, black/isort — all Passed.juniper-check-doc-linkswith the exact CI exclude set: PASSED (no markdown link targeted the deleted files; all refs were inline-code).See juniper-ml
notes/JUNIPER_2026-07-06_JUNIPER-ECOSYSTEM_LAUNCH-PATH-BIND-AUDIT.md(SEC-F25).🤖 Generated with Claude Code
https://claude.ai/code/session_01LX5ToumBaABH3QutQC86sM