Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Don't do it, you'll end up in a world of pain : https://jpetazzo.github.io/2015/09/...
-
What are all these comments. DID(docker in docker) is legit useful. The most widely used example is to setup CI runner slaves. Like gitlab runner. There is a docker image for the runner, so it is easy to setup a runner and make the host environment clean. The image also has a docker in it, so that for each build process the runner runs, you can setup a different environment dynamically without messing the environment in runner container. This way, it is easy to setup, cleanup and the runner is able to pick up any CI procedure and run in your specified enviroent.
-
@kevinye32 I gree, there are legit ways of doing DID, if you know what you are doing, but if you are just doing it for fun, or for a quick solution to a complex problem you are probably doing it wrong.
It is usually the case that people don't get it because DID is complex. -
@Avimelekh you should avoid that by mounting the native docker port inside the container which manages other docker containers.
This way any container orchestrated inside the orchestration container can mount volumes of the host running the orchestration container. -
@polaroidkidd should not be an issue while using user namespacing , not sure tho. I need to set DinD up in my kubernetes cluster and expose inside cluster as service with limted access to nfs provisoned volume shares within next month. Building my own ci service atm :P
-
CodeBane7736y@Mitiko huh? How you try without smoking? You mean taste? Cos that's a different word completely lool
Related Rants
what if we put docker inside a docker...
joke/meme
high
smoking
elon
docker