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

Error: pull image "docker.elastic.co/eck-dev/eck-operator-thb:1.7.0-SNAPSHOT-ff98c86" #5151

Closed
pabloandrei opened this issue Dec 9, 2021 · 6 comments

Comments

@pabloandrei
Copy link

pabloandrei commented Dec 9, 2021

Hello.

After applying the sample described at https://github.com/elastic/cloud-on-k8s/blob/1.9.0/config/all-in-one.yaml, I am getting the error below.

Would they know how to inform the workaround?
Sincereley, Pablo

  • ECK version: 1.9.0

  • Kubernetes information: microk8s (ubuntu)

  • kubectl version: Client Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.7-3+7700880a5c71e2", GitCommit:"7700880a5c71e25c44491ef5c7d7fb30527d8337", GitTreeState:"clean", BuildDate:"2021-11-17T22:07:23Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}

  • Resource definition: https://github.com/elastic/cloud-on-k8s/blob/1.9.0/config/all-in-one.yaml

  • Logs:

Failed to pull image "docker.elastic.co/eck-dev/eck-operator-thb:1.7.0-SNAPSHOT-ff98c869": rpc error: code = NotFound desc = failed to pull and unpack image "docker.elastic.co/eck-dev/eck-operator-thb:1.7.0-SNAPSHOT-ff98c869": failed to resolve reference "docker.elastic.co/eck-dev/eck-operator-thb:1.7.0-SNAPSHOT-ff98c869": docker.elastic.co/eck-dev/eck-operator-thb:1.7.0-SNAPSHOT-ff98c869: not found
@botelastic botelastic bot added the triage label Dec 9, 2021
@naemono
Copy link
Contributor

naemono commented Dec 9, 2021

Could you please let us know what documentation you were following that was referencing this file? Recent documentation (since 1.7) indicates using 2 separate files

https://www.elastic.co/guide/en/cloud-on-k8s/1.9/k8s-deploy-eck.html

kubectl create -f https://download.elastic.co/downloads/eck/1.9.0/crds.yaml
kubectl apply -f https://download.elastic.co/downloads/eck/1.9.0/operator.yaml

Let us know if we can go ahead and close this issue, thanks.

@thbkrkr
Copy link
Contributor

thbkrkr commented Dec 10, 2021

Sorry for the inconvenience, this file was accidentally committed.

@pabloandrei
Copy link
Author

Could you please let us know what documentation you were following that was referencing this file? Recent documentation (since 1.7) indicates using 2 separate files

https://www.elastic.co/guide/en/cloud-on-k8s/1.9/k8s-deploy-eck.html

kubectl create -f https://download.elastic.co/downloads/eck/1.9.0/crds.yaml
kubectl apply -f https://download.elastic.co/downloads/eck/1.9.0/operator.yaml

Let us know if we can go ahead and close this issue, thanks.

Exactly this...

@pabloandrei
Copy link
Author

kubectl apply -f https://download.elastic.co/downloads/eck/1.9.0/operator.yaml

Ill try now...

@pabloandrei
Copy link
Author

pabloandrei commented Dec 10, 2021

After uses of the new merge, I get other problem:

0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.

Follow below my sequence of commands:

> sudo snap install microk8s --classic
> microk8s enable dns
> microk8s enable storage
> microk8s enable ingress
> microk8s enable helm3
> microk8s helm3 repo add elastic https://helm.elastic.co
> microk8s helm3 repo update

> microk8s kubectl create -f https://download.elastic.co/downloads/eck/1.9.0/crds.yaml
> microk8s kubectl apply -f https://download.elastic.co/downloads/eck/1.9.0/operator.yaml


cat <<EOF | microk8s kubectl apply -f -
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: quickstart
spec:
  version: 7.16.0
  nodeSets:
  - name: default
    count: 1
    config:
      node.store.allow_mmap: false
EOF

image

@pabloandrei
Copy link
Author

pabloandrei commented Dec 10, 2021

After uses of the new merge, I get other problem:

0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
....

After reinstall Microk8s, the problem no more occurred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants