Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

nomad init example does not expose redis port #201

Closed
ghost opened this issue Oct 2, 2015 · 1 comment
Closed

nomad init example does not expose redis port #201

ghost opened this issue Oct 2, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 2, 2015

This may be related to a misreading of issue #185 or how the nomad init example file is supposed to work, however when scheduling the nomad init example redis instance port 6379 is not actually exposed on the docker host. Is this a placeholder example designed to just run the instance but not expose anything? Running example with count = 3 on a nomad 3 host cluster using master.

[core@bastion ~]$ nomad status example
ID          = example
Name        = example
Type        = service
Priority    = 50
Datacenters = dc1
Status      = <none>

==> Evaluations
ID                                    Priority  TriggeredBy   Status
9864da98-2599-ab05-9113-833e74d046d2  50        job-register  complete

==> Allocations
ID                                    EvalID                                NodeID                                TaskGroup  Desired  Status
3bbc0ca4-0e89-6f91-b1a5-bf7664ecae93  9864da98-2599-ab05-9113-833e74d046d2  f7acd13d-0aa7-1979-f837-eb10f618e455  cache      run      running
b3fad19f-2cd8-ec5a-972d-bb217461a299  9864da98-2599-ab05-9113-833e74d046d2  77ac8aed-5682-42df-636b-816d62808358  cache      run      running
c898bd51-0606-f098-b8b6-aad637f74a19  9864da98-2599-ab05-9113-833e74d046d2  4502db5c-ca0c-6850-09a7-4192754a9a6f  cache      run      running
[core@bastion ~]$ ansible all -m shell -a "docker ps"
10.42.0.62 | success | rc=0 >>
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
230983ae9282        redis:latest        "/entrypoint.sh redi   7 minutes ago       Up 7 minutes        6379/tcp            distracted_wilson

10.42.0.60 | success | rc=0 >>
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
56b382170ba2        redis:latest        "/entrypoint.sh redi   7 minutes ago       Up 7 minutes        6379/tcp            focused_galileo

10.42.0.61 | success | rc=0 >>
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
f60b767ce783        redis:latest        "/entrypoint.sh redi   7 minutes ago       Up 7 minutes        6379/tcp            naughty_babbage

No hosts are actually forwarding through to 6379. If this is by design it would probably be helpful to update the example with an image setup to forward through as it's a bit confusing. I'm of the understanding from issue #185 that my container process must read an environment variable to bind properly.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants