Skip to content

fix(security): remove MySQL and Redis port exposure to host#288

Merged
jakeaturner merged 1 commit intodevfrom
fix/mysql-redis-internal-only
Mar 19, 2026
Merged

fix(security): remove MySQL and Redis port exposure to host#288
jakeaturner merged 1 commit intodevfrom
fix/mysql-redis-internal-only

Conversation

@chriscrosstalk
Copy link
Collaborator

Summary

  • Removes ports: mappings for MySQL (3306) and Redis (6379) from the compose template
  • Both services are only accessed by the admin container via Docker's internal network (service names mysql and redis)
  • Redis has no authentication, so LAN exposure was unnecessary risk

Closes #279

Test plan

  • Fresh install: verify admin container connects to MySQL and Redis normally
  • Verify MySQL and Redis ports are no longer accessible from the host network
  • Verify all NOMAD features work (downloads, benchmarks, AI chat)

🤖 Generated with Claude Code

MySQL (3306) and Redis (6379) were published to all host interfaces
despite only being accessed by the admin container via Docker's internal
network. Redis has no authentication, so anyone on the LAN could connect.

Removes the port mappings — containers still communicate internally via
Docker service names.

Closes #279

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@chriscrosstalk chriscrosstalk added the enhancement New feature or request label Mar 17, 2026
@jakeaturner jakeaturner changed the base branch from main to dev March 19, 2026 16:46
@jakeaturner jakeaturner merged commit 55a5ab1 into dev Mar 19, 2026
@jakeaturner jakeaturner deleted the fix/mysql-redis-internal-only branch March 19, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: MySQL and Redis bound to all interfaces; use internal Docker networking only

2 participants