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

nodeup: Did not find docker package for xenial amd64 18.06.3 #6585

Closed
ChristopherHanson opened this issue Mar 6, 2019 · 4 comments · Fixed by #6965
Closed

nodeup: Did not find docker package for xenial amd64 18.06.3 #6585

ChristopherHanson opened this issue Mar 6, 2019 · 4 comments · Fixed by #6965

Comments

@ChristopherHanson
Copy link

1. What kops version are you running? The command kops version, will display
this information.

1.11.1

3. What cloud provider are you using?

AWS

4. What is the simplest way to reproduce this issue?

Create a cluster on AWS on ubuntu 16.04 (ami-0ad16744583f21877 in us-west-1) without specifying the Docker version in the cluster config.

5. What happened after the commands executed?

Docker is not installed on cluster ubuntu 16.04 cluster nodes and the cluster fails to start; journalctl on the nodes reports:

Mar 05 23:16:21 ip-10-0-16-11 nodeup[1819]: W0305 23:16:21.306809    1819 docker.go:860] Did not find docker package for xenial amd64 18.06.3

6. What did you expect to happen?

kops should install Docker 18.06.3 by default on all cluster nodes

9. Anything else do we need to know?

Setting a docker version to the previous release in the cluster config build the cluster successfully:

spec:
  docker:
    version: 18.06.2
@bhvishal9
Copy link

Was it fixed? We are still getting this issue on kops Version 1.12.0-beta.1.

@apjneeraj
Copy link

we have the same issue while upgrading cluster from 1.11.x to 1.12.x with kops 1.12.0-beta.2.

systemd[1]: Started Kubernetes Protokube Service.
-- Subject: Unit protokube.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit protokube.service has finished starting up.
--
-- The start-up result is done.
May 08 19:16:29 ip-172-5-61-100 systemd[13490]: protokube.service: Failed at step EXEC spawning /usr/bin/docker: No such file or directory
-- Subject: Process /usr/bin/docker could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

@ChristopherHanson
Copy link
Author

Does the workaround of setting the docker and version keys in the cluster config work for either of you? That is essentially how we "solved" the issue, e.g.:

apiVersion: kops/v1alpha2
kind: Cluster
metadata:
  name: example-cluster
spec:
  docker:
    version: 18.06.2

Not sure we've tried anything beyond 18.06.2 at this point though.

@adammw
Copy link
Contributor

adammw commented May 13, 2019

18.06.3 seems only to be defined for Ubuntu Bionic (18.04), not Ubuntu Xenial (16.04), even though there are packages for it on the Docker download site.

https://github.com/kubernetes/kops/blob/master/nodeup/pkg/model/docker.go

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

Successfully merging a pull request may close this issue.

4 participants