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

minikube v1.12.3 faild to start on Centos 7.4.1708 #9075

Closed
lordk911 opened this issue Aug 25, 2020 · 7 comments
Closed

minikube v1.12.3 faild to start on Centos 7.4.1708 #9075

lordk911 opened this issue Aug 25, 2020 · 7 comments
Labels
co/docker-driver Issues related to kubernetes in container kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@lordk911
Copy link

lordk911 commented Aug 25, 2020

$ docker -v
Docker version 17.03.2-ce, build f5ec1e2

$ minikube start --cpus=4 --memory=4096mb --driver=docker

  • minikube v1.12.3 on Centos 7.4.1708
  • Using the docker driver based on user configuration
  • Starting control plane node minikube in cluster minikube
  • Pulling base image ...
  • Creating docker container (CPUs=4, Memory=7900MB) ...
  • Stopping node "minikube" ...
  • Powering off "minikube" via SSH ...
  • Deleting "minikube" in docker ...
    ! StartHost failed, but will try again: creating host: create: creating: prepare kic ssh: copying pub key: docker copy /tmp/tmpf-memory-asset543657973 into minikube:/home/docker/.ssh/authorized_keys, output: unknown shorthand flag: 'a' in -a
    See 'docker cp --help'.
    : exit status 125
  • Creating docker container (CPUs=4, Memory=7900MB) ...
  • Failed to start docker container. "minikube start" may fix it: creating host: create: creating: prepare kic ssh: copying pub key: docker copy /tmp/tmpf-memory-asset080548560 into minikube:/home/docker/.ssh/authorized_keys, output: unknown shorthand flag: 'a' in -a
    See 'docker cp --help'.
    : exit status 125
@afbjorklund
Copy link
Collaborator

afbjorklund commented Aug 25, 2020

Basically the Docker version is too old, only 19.03 is tested on a regular basis

Kubernetes itself supports older versions, but Minikube does not (yet, anyway)

@afbjorklund afbjorklund added co/docker-driver Issues related to kubernetes in container priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. kind/bug Categorizes issue or PR as related to a bug. labels Aug 25, 2020
@lordk911
Copy link
Author

ok thanks

@afbjorklund
Copy link
Collaborator

afbjorklund commented Aug 25, 2020

Upgrading docker might help https://docs.docker.com/engine/install/centos/

Note that CentOS 7.4 is not supported (by Docker)

To install Docker Engine, you need a maintained version of CentOS 7.
Archived versions aren’t supported or tested.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 23, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 23, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/docker-driver Issues related to kubernetes in container kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

4 participants