Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

port vs.expose #177

Closed
gimler opened this issue Nov 22, 2016 · 2 comments
Closed

port vs.expose #177

gimler opened this issue Nov 22, 2016 · 2 comments

Comments

@gimler
Copy link

gimler commented Nov 22, 2016

When using docker-compose i would check if a container has a specific port exposed.

version: '2'
services:
  service:
    ...
    expose:
      - "9000"

this doesn't work

port:
  tcp:9000:
    listening: true
    ip:
    - 0.0.0.0

output

.......FS.................

Failures/Skipped:

Port: tcp:9000: listening:
Expected
    <bool>: false
to equal
    <bool>: true
Port: tcp:9000: ip: skipped

Total Duration: 0.101s
Count: 26, Failed: 1, Skipped: 1

netstat -lnt

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 127.0.0.11:35818        0.0.0.0:*               LISTEN      
tcp        0      0 :::9000                 :::*                    LISTEN
@aelsabbahy
Copy link
Member

aelsabbahy commented Nov 22, 2016

Try using tcp6:9000 in the goss check, I think this is related to #149

@gimler
Copy link
Author

gimler commented Nov 22, 2016

this works as expected

port:
  tcp6:9000:
    listening: true
    ip:
    - '::'

@gimler gimler closed this as completed Nov 22, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants