3 ms·
> Indeed. If you think of the docker image itself as an executable format like PE or ELF, this becomes clearer. But I don’t, because a docker image will not ru
by tomcam 4y ago
> Indeed. If you think of the docker image itself as an executable format like PE or ELF, this becomes clearer.
But I don’t, because a docker image will not run without docker. A standalone, executable file can be distributed and deployed all by itself. A docker image cannot.
- crote 4y agoA standalone executable doesn't remain a standalone executable for very long, though. You need something to handle its lifecycle and restart it when it dies. You need something to handle logging. You need something to jail it and prevent it from owning your system when it has a bug. You need something to pass it database credentials. You need something to put a cpu/mem limit on it. Not to mention that most executables aren't standalone but depend on system libraries. A lot of that can be handled by systemd these days. But now you have a single standalone executable, its mandatory companion config files, and all its dependencies. Docker was designed to create a platform where the only dependency is Docker itself, and it does that job reasonably well.
- candiodari 4y agoThat used to be apache and mod_* (mod_php, mod_python, mod_ruby, ...) I've always wondered if it is possible to extend this system. Mod_docker?
- lmm 4y ago"By itself" where? You're going to toggle it in on the front panel? If you want to run an executable you have to have some kind of service (in the broad sent) set up to receive it and run it. Same with a docker image. Those services are, if anything, more readily available and standardised for docker than they are for executables.