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

running rke up multiple times results with lots of orphaned container volumes #1074

Closed
aemneina opened this issue Jan 2, 2019 · 2 comments
Closed
Assignees
Milestone

Comments

@aemneina
Copy link
Contributor

aemneina commented Jan 2, 2019

RKE version:
rke version v0.1.11

Docker version: (docker version,docker info preferred)
17.06.2

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
ubuntu 16.04

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS

cluster.yml file:

Steps to Reproduce:
just run rke up a couple times, didnt even need to change anything in the yaml and saw a growth of 10 new volumes.

Workaround:
docker volume prune should do the trick to reclaim some space

Results:
could run out of disk space if one has a smaller volume and runs rke up a few times.

@alena1108 alena1108 added this to the v0.2.0 milestone Jan 7, 2019
@galal-hussein
Copy link
Contributor

@aemneina I was able to find the root cause of this problem, the sidecar container is upgraded 5 times everytime rke runs, the sidecar container is used with k8s components to provide several helper scripts for cloud provider configuration, etc.

@sangeethah
Copy link

Reproduced this issue with v0.1.11

This issue does not happen when testing with v0.2.0-rc5.

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

6 participants