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

toolbox depends on running Docker daemon #1704

GreatSUN opened this Issue Dec 12, 2016 · 2 comments


None yet
5 participants

GreatSUN commented Dec 12, 2016

Issue Report

When trying to use toolbox on our Kubernetes clusters running on rkt, we see that we would either have to run the Docker daemon or to setup the Containers our self.

As discussed with @euank


Toolbox should not be depending on a running Docker daemon, instead it would be nicer if Toolbox would make use of rkt which basically doesn't require anything.

CoreOS Version




Kubernetes 1,4.6
rkt 1.21.0

What hardware/cloud provider/hypervisor is being used to run CoreOS?
Bare metal

Expected Behavior

Toolbox is not depending on running Docker daemon

Actual Behavior

Toolbox is only working when Docker is enabled

Reproduction Steps

Run toolbox after disabling Docker

Feature Request

Make Toolbox independent from Docker

Desired Feature

Toolbox is independent from Docker


This comment has been minimized.


euank commented Dec 12, 2016

The code in toolbox in question:

Since rkt, as of several releases ago, has an export command, it might be appropriate to use that there, though one regression it would introduce is requiring more space during extraction since it doesn't support streaming to stdout currently.

This would also be fixed with the change suggested in #1610

cc @lucab @dm0-


This comment has been minimized.

glevand commented Jan 11, 2017

For this change to work on arm64 we need rkt/rkt#3526 (fetch: arch messed up) fixed.

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