Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

--bc fails for Elasticsearch #1566

Open
v1v opened this issue Feb 27, 2023 · 0 comments
Open

--bc fails for Elasticsearch #1566

v1v opened this issue Feb 27, 2023 · 0 comments

Comments

@v1v
Copy link
Member

v1v commented Feb 27, 2023

Given the current Build Candidate pointing to 8.7.0
When running ./scripts/compose.py start 8.7.0 --bc
Then it fails with

Error response from daemon: manifest for docker.elastic.co/elasticsearch/elasticsearch:8.7.0 not found: manifest unknown: manifest unknown

That's related to a known issue with the upstream, since the docker images based on .tar.gz are not tagged with the required tags related to the version.

For instance, the manifest.json from the Elasticsearch docker context .tar.gz

manifest.json | jq .
[
  {
    "Config": "8aa89874e35b45cee1374f154179dda6bcfd5476ff78a59b8dfcccc50724ce18.json",
    "RepoTags": [
      "elasticsearch:x86_64"
    ],

while a similar manifest.json for a different stack product got different repo tags:

[
  {
    "Config": "838b7fd41341b6a601e1f52d073017b81f41f2b1a7e0ccbe1c3da3030afe5983.json",
    "RepoTags": [
      "docker.elastic.co/kibana/kibana:8.7.0

Workaround

As long as it's not fixed in the upstream it's required to manually run the below commands after hitting the above-mentioned error:

docker pull docker.elastic.co/observability-ci/elasticsearch:8.7.0
docker tag docker.elastic.co/observability-ci/elasticsearch:8.7.0 docker.elastic.co/elasticsearch/elasticsearch:8.7.0

or look for the docker image Id and retag it, in case the docker image is not available in docker.elastic.co/observability-ci/

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

1 participant