[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]

Re: [atomic] atomic run/LABEL RUN issue when exposing container ports to the host

From: Colin Walters <walters verbum org>
To: Avesh Agarwal <avesh ncsu gmail com>, atomic projectatomic io
Subject: Re: [atomic] atomic run/LABEL RUN issue when exposing container ports to the host
Date: Mon, 24 Aug 2015 16:12:09 -0400

On Wed, Aug 19, 2015, at 03:42 PM, Avesh Agarwal wrote:

Hi,

I am having issues with "atomic run" and also with LABEL RUN where the exposed ports in container are not being published to the host. I have following in Dockerfile:

LABEL RUN="docker run -d -p 4001:4001 -p 7001:7001 -p 2379:2379 -p 2380:2380 IMAGE"

Ah...this is because /usr/bin/atomic originated for use with SPCs...it has `--net=host` hardcoded, which breaks port mappings.

We're going to need more semantic work in /usr/bin/atomic to support non-SPC cases. This is probably best discussed in an issue on projectatomic/atomic; want to file it?

Follow-Ups:
- Re: [atomic] atomic run/LABEL RUN issue when exposing container ports to the host
  - From: Avesh Agarwal

References:
- [atomic] atomic run/LABEL RUN issue when exposing container ports to the host
  - From: Avesh Agarwal

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]