I was looking for the chronograf v1.11.4 docker image for a recent fix, but
a) https://quay.io/repository/influxdb/chronograf does not list any of the 1.11 series releases as tags, even if it is specified in the release message
b) 1.11.3 seems to be the latest released over at docker hub
c) The release message specifies quay.io image repository, but chronograf readme specifies pulling from default image repository, which, for most people I assume will be the docker hub https://github.com/influxdata/chronograf#with-docker
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
- run
docker pull quay.io/influxdb/chronograf:1.11.4
- Observe error response from daemon
Expected behavior:
Docker image is pulled
Actual behavior:
Docker image doesn't exist, and is therefore not retrieved
Environment info:
- Chronograf version: v1.11.4
- Other relevant environment details: Ubuntu
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Logs:
Include a snippet of errors in the log.
I was looking for the chronograf v1.11.4 docker image for a recent fix, but
a) https://quay.io/repository/influxdb/chronograf does not list any of the 1.11 series releases as tags, even if it is specified in the release message
b) 1.11.3 seems to be the latest released over at docker hub
c) The release message specifies quay.io image repository, but chronograf readme specifies pulling from default image repository, which, for most people I assume will be the docker hub https://github.com/influxdata/chronograf#with-docker
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
docker pull quay.io/influxdb/chronograf:1.11.4Expected behavior:
Docker image is pulled
Actual behavior:
Docker image doesn't exist, and is therefore not retrieved
Environment info:
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Logs:
Include a snippet of errors in the log.