-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Docker containers are started with image Id(sha256) instead of actual image name:tag #2624
Comments
We encounter the same issue. We use the docker tag to follow performance berween versions and to group logs. |
Same issue here. We found it in metrics using Telegraf. |
@dadgar Sorry to bug you. This is something critical for us. All our alerting system depend on it. Right now all our alerts are not working. Is there any ETA do you have in your mind. If you point me place in the code i can fix and raise an pull request. |
@dadgar We solved this using docker labels. telegraf 1.3.0 supports docker labels and nomad supports docker labels 👍 💯 Please feel free to close this. |
Thanks for updating! I would like to keep this open a little longer so that I can investigate if we can use the name:tag |
Any news regarding this? It seems strange that Nomad has |
We're just now noticing this as we start to support our nomad clusters. It can make it difficult to identify the container you may need to kill or inspect, etc. any way of using the image name yet? |
We would like to use watchtower for auto updating our containers. But the naming of the image prevents it from detecting the correct docker hub repository. |
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 filing a bug please include the following:
Nomad version
Nomad v0.5.6
Operating system and Environment details
Ubuntu 16.04.2 LTS
Linux container3.xxx.internal 4.4.0-1016-aws #25-Ubuntu SMP Thu Apr 20 11:34:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Issue
When a docker container is started by nomad client the Image Attribute of docker inspect now show sha256:378c11e45c5a0d5decc96531b55841162924b83b3e7166980fb3c886337f245b instead of user friendly image name and Tag.
Job file (if appropriate)
config {
image = "docker-registry.xxx.internal/xxx/content-generator:59"
port_map {
nginx = 80
}
}
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
20ddd4688a64 378c11e45c5a "/usr/bin/supervis..." 13 minutes ago Up 13 minutes 10.20.13.4:52907->80/tcp, 10.20.13.4:52907->80/udp content-xx-rr-f80b3386-0009-030d-0f45-e5a749bde149
In the above output Image Column used to give user friendly Image name:ImageTag Instead now it gives the imaged id.
We use telegraf to collect container level metrics. Telegraf user docker Image name and Tag to differentiate between container metrics. Now all we get is image Sha256 Id.
Please let me know if you need any further details
The text was updated successfully, but these errors were encountered: