rkt/rkt

Expose port only on loopback device

Open

#2,230 opened on Feb 25, 2016

View on GitHub
 (9 comments) (1 reaction) (0 assignees)Go (865 forks)batch import
area/networkinghelp wantedkind/support

Repository metrics

Stars
 (8,871 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

My current setup uses docker containers that expose their ports only on localhost and are accessible via a reverse proxy from the outside world. Now I wanted to switch some services to rkt, but I couldn't get it managed to expose ports only on localhost. In fact, the rkt container was accessible from everywhere but not from localhost. I tried to run a gogs git server like this: sudo rkt run --insecure-options=image --port=3000-tcp:3000 docker://gogs/gogs. Is it possible to publish ports only on localhost with rkt run?

Contributor guide

Research direction
Investigate whether rkt's port mapping supports binding to specific IP addresses like 127.0.0.1. If not, explore how to add that feature or suggest workarounds such as using iptables or a reverse proxy.
Tech stack
go
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
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.
65