-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Update docker-compose.yml to add 'dind' #1655
Conversation
Add 'dind' image to run docker-in-docker: issue #1653
I do not know why but the pull request #1655 has lost the 'networks' code. I'll try to insert it Insert again ;-)
Add 'dind' image to run docker-in-docker: issue laradock#1653
I do not know why but the pull request laradock#1655 has lost the 'networks' code. I'll try to insert it Insert again ;-)
@vlauciani What was the purpose of adding this? I can't find any mention of it in the documentation. I have a hard time imagining why php-fpm, for example, would need to manage its own docker containers, and the security implications frighten me. Perhaps I'm missing something, though. At the very least there should probably be a warning about how insecure this is. |
Hi @hackel I work in a research Italian Institute and we are “deckerizing” our procedures, scripts and software. For example if I would run a simple “hello world” docker from Laravel framework using Laradock you I to:
Will be my care to update the documentation. |
Hi, Thanks. |
While I can see that @vlauciani has a valid use case for this feature, I'm surprised this feature was merged as a default for all Laradock users without questioning the security of giving php-fpm access to the Docker runtime if it isn't needed for operation. I think this needs to be turned off by default, with the option to turn it on for these (assuming) rare use cases. |
@vlauciani sorry but I can't understand how to deploy "hello-world" container into "php-fpm" and run it from. Could you explain it? Thanks. |
Hi @dlnsk First of all you need to install
then, you can install
Or, as in my case, you can build your own image:
this is a very good solution... but I understand that |
Add 'dind' image to run docker-in-docker: issue #1653
I completed the 3 steps below: