Why is it better to split docker containers (like LAMP stack)with docker compose than have them combined in one container?

• PeerTube

  409 12,555 9.9 TypeScript

  ActivityPub-federated video streaming platform using P2P directly in your web browser

For example I run PeerTube via its docker-compose.yml https://github.com/Chocobozzz/PeerTube/blob/develop/support/docker/production/docker-compose.yml and what you can see is that out 6 images 4 are not from PeerTube. They are by the official project e.g. certbot/certbot or postgres:13-alpine which means I'm confident that these images are correct in terms of running at all but also, hopefully, efficiency and security. The alternative would be 1 single PeerTube image managing dependencies at the package level and would mean losing all the benefits you initially mentioned and bringing the complexity back to the project maintainer.

• Docker-OSX

  132 35,279 5.7 Shell

  Run macOS VM in a Docker! Run near native OSX-KVM in Docker! X11 Forwarding! CI/CD for OS X Security Research! Docker mac Containers.

Docker monitors a single process to determine that the container is down and may need restarting. It’s a convention. https://github.com/sickcodes/Docker-OSX is an image that started is a container with many hundreds of dissimilar processes. Misuse perhaps, but I have it going for a purpose, even though I have real Macs in the house too.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project