The configuration or environment part of the wizard should show a way of adding exposed ports. The Docker Remote API supports it but Fog doesn't yet. Assume Fog does support it as I have a patch pending review. The format for exposed ports goes like <pre> { "ExposedPorts" : [ "22/tcp": {}, "80/tcp": {}] } </pre> Yes, key is the port/protocol, value is.. nothing?
Created from redmine issue http://projects.theforeman.org/issues/7864
Moving to POST since upstream bug http://projects.theforeman.org/issues/7864 has been closed ------------- Vanya Jauhal Applied in changeset commit:foreman-docker|8e2848d58b12a71a89f19e6eb98be790d5f19067.
*** Bug 1231361 has been marked as a duplicate of this bug. ***
*** Bug 1231360 has been marked as a duplicate of this bug. ***
*** Bug 1231359 has been marked as a duplicate of this bug. ***
Hi, please provide verification steps thanks in advance Thanks and Regards, Tazim
VERIFIED. @Sat6.2.0-Beta tfm-rubygem-foreman_docker-2.0.1.4-1.el7sat.noarch 1) Start creating a container, into Command enter "python -m SimpleHTTPServer 12345" and Add Exposed Port 12345/tcp 2) Run the container and check its IP address 3) Check the container info at host @docker_host # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 651f1720780c <registry>:443/rhel6.8:latest "python -m SimpleHTTP" About an hour ago Up About an hour 123/udp, 12345/tcp rhel68_python 3) Connect to the exposed port @docker_host # nc <IP address> 12345 GET / <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html> ... 4) Check UI Logs tab for a connection record Serving HTTP on 0.0.0.0 port 12345 ... 172.17.0.1 - - [11/May/2016 07:55:15] "GET /" 200 - + I tested the same with UDP port + I tested that wrong values for port number are handled correctly
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501