Closed xsak closed 2 years ago
Are you sure you're getting the latest image and not just using a cached one?
If I delete my image, pull it again, and start up docker-compose, I get 4.2.4
.
donald@laptop:~/src/docker-compose$ docker rmi graylog/graylog-enterprise:4.2
Error: No such image: graylog/graylog-enterprise:4.2
donald@laptop:~/src/docker-compose$ docker pull graylog/graylog-enterprise:4.2
4.2: Pulling from graylog/graylog-enterprise
e5ae68f74026: Already exists
9e9f5b9b70c2: Already exists
4609c07167c7: Already exists
a29221198438: Already exists
96a83e581e12: Pull complete
f15934a93e2f: Pull complete
18b3d74286e2: Pull complete
f37a4b429135: Pull complete
Digest: sha256:fda2659b9ce0be84c088eb3923cd281f750abfdb7dda329b1da2443c430e1eb6
Status: Downloaded newer image for graylog/graylog-enterprise:4.2
docker.io/graylog/graylog-enterprise:4.2
donald@laptop:~/src/docker-compose/open-core$ docker-compose up
Starting open-core_mongodb_1 ... done
Starting open-core_elasticsearch_1 ... done
Creating open-core_graylog_1 ... done
[...]
graylog_1 | 2021-12-17 21:18:34,910 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server up and running.
donald@laptop:~/src/docker-compose/open-core$ curl -u admin:***** -H 'Accept: application/json' -X GET 'http://localhost:9000/api/cluster?pretty=true'
{
"e1e63793-16e0-4872-a91e-6f129d382550" : {
"facility" : "graylog-server",
"codename" : "Noir",
"node_id" : "e1e63793-16e0-4872-a91e-6f129d382550",
"cluster_id" : "e20030eb-467c-4e56-be21-124f2e41a310",
"version" : "4.2.4+b643d2b",
"started_at" : "2021-12-17T21:18:29.707Z",
"hostname" : "63fba428b9c1",
"lifecycle" : "running",
"lb_status" : "alive",
"timezone" : "Etc/UTC",
"operating_system" : "Linux 5.4.0-91-generic",
"is_processing" : true
}
}
Yes, it was cached. Sorry.
The new
graylog/graylog-enterprise:4.2
image (released on 06.12.) is actually v4.2.3, but it should be v4.2.4.