You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
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.
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.
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
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
Bug
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
ALL
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
Environment
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
The text was updated successfully, but these errors were encountered: