-
Notifications
You must be signed in to change notification settings - Fork 886
rkt: run dockerd #638
Comments
If you don't have aufs support enabled (debian has it by default) docker will try to use the devicemapper Storage Driver. This will not work because it uses loop devices which are not inside the container. I could make it work with the overlay Storage Driver. |
I think it is fine if we have to be a little more restrictive about what storage backends can be used running it inside Rocket; in CoreOS itself we can always rely on overlayfs |
The script to build the docker aci has been merged (appc/build-repository#1). The instructions how to use the docker aci can be found on: So I think this issue can be closed. |
awesome! |
I added more details on appc/build-repository#6 I'm unsure about adding the Dockerfile from the Docker-in-Docker in build-repository: if Docker-in-Docker gets updated upstream, it would be easier to get them if we keep the same repository structure rather than copying the files in build-repository. |
That's fine, I missed that it was based on that. Thanks! |
As part of #13, it would be nice to be able to run dockerd from within a Rocket pod.
(thinking out loud), while dockerd is running under Rocket, we could mimic the Docker client on the host with something like
alias docker="rkt enter $RKT_DOCKER_UUID docker run $@"
or similarLatest status from #13 (comment):
Since #626 is merged, running Dockerd inside Rocket works fine as long as the isolator "os/linux/capabilities-retain-set" contains CAP_NET_ADMIN. The test was reported on this issue. The dind aci was generated by docker2aci.
We don't have a solution to modify automatically the isolator in the aci. Flannel would also benefit from that, see this comment.
The text was updated successfully, but these errors were encountered: