Timeline for Why is Docker-in-Docker considered bad?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2023 at 14:42 | comment | added | Shanteva | Oh great, now you can't run docker directly in k8s since 1.24 without a custom AMI, so I don't think so @Gulzar in fact, trying to find the current best practice has been a nightmare for me | |
| Jan 24, 2022 at 13:33 | comment | added | Gulzar | Is this answer still updated, or is there a real solution nowadays? | |
| Nov 15, 2021 at 14:54 | comment | added | Segfault | -1 this answer answer has several problems. CI/CD systems are better if they are stateless. You're not storing session data or anything related to runtime operations in the filesystem of your container! "Sometimes filesystems just don't play well with each other when they're nested in this way" <-- citation needed. Using docker-in-docker for CICD is now a standard practice, in fact both GitLab and GitHub have this as an officially supported configuration for their CICD systems. | |
| S Apr 5, 2018 at 15:55 | history | suggested | Scott Stensland | CC BY-SA 3.0 |
fixed bad link
|
| Apr 5, 2018 at 15:34 | review | Suggested edits | |||
| S Apr 5, 2018 at 15:55 | |||||
| Nov 12, 2017 at 11:41 | comment | added | helmesjo |
From this explanation I still can't really tell if dind should be avoided in my case... My build agent runs in a docker container, and does the following: 1. Checkout repo. 2. Start container & mount repo. 3. Run some build-/test script inside container. Per agent, there is ever only one 'dind'-container running. Are there still issues with dind in this use-case?
|
|
| Mar 27, 2017 at 23:26 | comment | added | rombob | Here's one example of described approach (dood) for Jenkins, yet several issues reported while using it hub.docker.com/r/psharkey/jenkins-dood | |
| Mar 27, 2017 at 21:04 | vote | accept | Richard Slater | ||
| Mar 27, 2017 at 2:59 | history | answered | Peter G | CC BY-SA 3.0 |