realpython/dockerizing-django

Aren't there secure issues since we expose 6379:6379

Open

#35 opened on Aug 26, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (493 forks)batch import
hacktoberfest

Repository metrics

Stars
 (1,326 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

https://github.com/realpython/dockerizing-django/blob/master/docker-compose.yml wrote

redis:
  restart: always
  build: ./redis
  ports:
    - "6379:6379"

I think this may expose 6379 to the whole internet? Although in production.yml changed to

ports:
  - "6379"

it expose a random port to the whole internet

And from compose file reference https://docs.docker.com/compose/compose-file/#/ports there is a format

ports:
   - "127.0.0.1:8001:8001"

Would this be safer? Any ideas?

Contributor guide

Research direction
Update docker compose.yml to bind Redis port to 127.0.0.1 to prevent public exposure.
Tech stack
python
Domain
backendsecurity
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80