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

Deploy a Replicated Stateful Application getting fails with Error: ErrImagePull #46253

Open
Sivakajan-tech opened this issue May 7, 2024 · 8 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Sivakajan-tech
Copy link

This is a Bug Report
I tried to deploy a Replicated Stateful Application(MySQL) with the guidance of this documentation in the kubernetes. I tried this in the minikube in Ubuntu 22.04.4 LTS. When I apply the service, config and the statefulset yaml file, I got an error of Init:ImagePullBackOff. and only one pod get exposed.(expected 3)

Screenshot 2024-05-07 at 20 58 25

And also when I check the events I got the following response.

19m         Warning   Failed             pod/mysql-0         Error: ErrImagePull
15m         Normal    BackOff            pod/mysql-0         Back-off pulling image "gcr.io/google-samples/xtrabackup:1.0"
19m         Warning   Failed             pod/mysql-0         Error: ImagePullBackOff
11m         Normal    Scheduled          pod/mysql-0         Successfully assigned default/mysql-0 to minikube
11m         Normal    Pulled             pod/mysql-0         Container image "mysql:5.7" already present on machine
11m         Normal    Created            pod/mysql-0         Created container init-mysql
11m         Normal    Started            pod/mysql-0         Started container init-mysql
10m         Normal    Pulling            pod/mysql-0         Pulling image "gcr.io/google-samples/xtrabackup:1.0"
10m         Warning   Failed             pod/mysql-0         Failed to pull image "gcr.io/google-samples/xtrabackup:1.0": [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of gcr.io/google-samples/xtrabackup:1.0 to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
10m         Warning   Failed             pod/mysql-0         Error: ErrImagePull
103s        Normal    BackOff            pod/mysql-0         Back-off pulling image "gcr.io/google-samples/xtrabackup:1.0"
10m         Warning   Failed             pod/mysql-0         Error: ImagePullBackOff

I want to deploy a MySQL stateful set with 3 instances using a common storage as the storage.

Page to Update:
https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/#statefulset

Kubernetes Version
$ kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0

@Sivakajan-tech Sivakajan-tech added the kind/bug Categorizes issue or PR as related to a bug. label May 7, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 7, 2024
@pranav-pandey0804
Copy link
Contributor

/sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label May 7, 2024
@sftim
Copy link
Contributor

sftim commented May 7, 2024

/remove-sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. and removed sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels May 7, 2024
@sftim
Copy link
Contributor

sftim commented May 7, 2024

The page doesn't specify AMD64 CPU as a requirement. As a minimum change, it should.

@Sivakajan-tech
Copy link
Author

Sivakajan-tech commented May 7, 2024

@sftim Could you please give me the corrected code?. I don't know where to specify that. THis could be helpful for others also.

@sftim
Copy link
Contributor

sftim commented May 7, 2024

Could you please give me the corrected code?. I don't know where to specify that. THis could be helpful for others also.

Someone (probably not me) would need to write the updated page. Right now, that has yet to happen.

@Sivakajan-tech
Copy link
Author

@sftim Could you suggest the code please? That would be helpful for now....

@sftim
Copy link
Contributor

sftim commented May 8, 2024

I don't plan to put time into working out any part of the specific page changes that are needed; I am confident I have plenty of other contribution work already planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

4 participants