3 ms·
Containers work particularly well for python environments. You can get them working locally, but it's easiest when the developers stick with the standard libra
by falcolas 4y ago
Containers work particularly well for python environments.
You can get them working locally, but it's easiest when the developers stick with the standard library. Needless to say, virtually nobody does.
- PurpleRamen 4y agoBut are containers portable? Can you take them, send them per mail or put on a USB-stick? And I'm not talking about the recipe for creating them, but the actual container itself.
- falcolas 4y agoYes. The actual image is a tar file, and container runtimes include commands for both exporting and importing. Exceptionally portable. More portable than JAR files and Go binaries, at least.
- PurpleRamen 4y agoWait, which container are we talking about? Docker? AppImage? Kubernetes? What about the runtime?
- jrockway 4y agoOCI Images. You can run them in Docker, Podman, Kubernetes, systemd-nspawn, etc. Nobody is going to use your tool if they have to fetch it from a container registry and have to run it isolated from their filesystem and network, though. OCI images are fine if you have a pet app and you have to ship it to a production server. Not that convenient for interactive tools, though. Consider: $ docker run -v /tmp/foobar:/tmp/foobar debian:stable ls /tmp/foobar a.txt You really just want to type "ls /tmp/foobar".
- falcolas 4y agoThat's something that aliases excel at.