compose

There was a thing in February where Python cryptography required rust, which broke docker-compose installs via pip. [1] There was a fair amount of back and forth about version pinning—it affected a lot of builds. Even the issue on the crypto package about it was fairly tense. Iirc, the dependency was rolled back. [1] https://github.com/docker/compose/issues/8105#issuecomment-7...

How awesome would it be if we could exclude specific dirs or files from bind mounts. Think of cache directories, log files, and, of course, node_modules. The common workaround to this, is to create an empty volume and map whatever you don't want mounted to it. You'll end up with an empty directory in your host system, but its contents are available from within the container. It has many problems though, mostly permission and ownership related, but it somehow makes Docker for Mac even slower and crash even more often than usual. Example minimal docker-compose.yaml file for a custom "devcontainer" we use in VSCode that showcases the workaround: version: '3.8' services: project: image: devcontainer:dev container_name: devcontainer build: context: . dockerfile: Dockerfile args: ALPI

I've been waiting for two features from Docker: 1. Launch a container by specifying its image digest, not image ID [0] [1]. You can pull an image with a specific digest, but then it gets an ID that is unique to the image repository. Later deployments must use that different image ID. This makes deployment tooling needlessly complicated. And it breaks the security guarantees of the digest by allowing the repository to modify the image. 2. Copy a file into a container with docker-compose, without requiring Swarm [1]. Do financial problems explain their slowness? I wish they would just charge $100/year per seat for Docker for macOS and then fix the long-standing problems. And sell a hosted tool to do trusted builds of docker images from hashed sources. Reproducible builds would be great, too. [0] https://github.com/moby/moby/issues/164