is published_ports broken?

41 views
Skip to first unread message

spig...@gmail.com

unread,
Feb 11, 2020, 1:55:06 PM2/11/20
to molecule-users
Hi.
I have platforms with sidecar

platforms:
  - name: target
    image: centos/systemd
    pre_build_image: True
    privileged: true
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
      - /var/run/docker.sock:/docker.sock
    command: "/usr/sbin/init"
  - name: vault
    image: vault:1.3.1
    exposed_ports:
      - "8200/tcp"
    published_ports:
      - "127.0.0.1:8200:8200/tcp"


But it not seems to be working.

CONTAINER ID        IMAGE                           COMMAND                  CREATED             STATUS              PORTS               NAMES
f7e433bcdf37        molecule_local/vault:1.3.1      "docker-entrypoint.s…"   16 seconds ago      Up 15 seconds       8200/tcp            vault
53742c8f716d        molecule_local/centos/systemd   "/usr/sbin/init"         17 seconds ago      Up 16 seconds                           target
Ports do not published on host.
Reply all
Reply to author
Forward
0 new messages