cli VS Docker Compose

I am a self-employed furniture maker. I'm that guy who somewhat infamously no longer builds software[0]. About a year ago I moved my operations from a makerspace to my own shop. That's come with its ups and downs.

On the one hand, I know which idiot last used a tool: me.

On the other, I would no longer see other humans besides my wife most weeks. To keep sane I also work one day a week at a bike shop fixing bikes. It's something I'd done on a volunteer basis many years back.

The unexpected nice thing about this is that it gives me projects that are an hour or two in size in addition to the many-week sized projects that I do as part of my business. It's sort of like getting to fix a small bug in the midst of adding a big feature; it lets me pop out of the big project for a bit and see something else through from start to finish and see some tangible progress before diving back into a long-running project that moves forward in fits and starts.

Beyond getting to tackle some bite-sized projects, I'd say the thing that sustains me is getting to work with clients. It's tons of fun when people come to me with a vision that we can iterate on and bring into reality. And then the flip side is also rewarding: getting to scratch an itch and turn a design I've been turning over in my mind into reality.

https://github.com/docker/cli/issues/267#issuecomment-695149...

Furniture making

On the topic of alternatives I use https://fishshell.com/ and have the Docker Completions installed.

More cases like this (but don't seem to have a consensus): https://github.com/docker/cli/issues/2686

anything happening with this that anyone is aware of: https://github.com/docker/cli/issues/2802

I found a few different issues in docker tracker about this issue, but the only one which seems to be merged is this one which has docker ignore any options which start with x- but that doesn't seem to help here as the local log driver then just complains about:

The service in the error is about docker swarm (that you didn't mention). It seems like you have an issue similar to this one: https://github.com/docker/cli/issues/2875

Docker itself is open-source, and has slowly been broken down into modular components that are themselves open-source. For example, most of what "run this Docker container" does has been extracted out into containerd, which is Apache licensed and used by lots of things. The Docker CE engine is now based on Moby, also Apache license, and the docker command line tool is also Apache licensed. I expect these tools to continue to be community-maintained (though maybe without the Docker name) due to their immense popularity even Docker Inc folds.

Docker has a bunch of components, including the CLI, a runtime etc. They're pretty much all definitely open source, e.g.: https://github.com/docker/cli

Solutions are many, and could include Docker Compose, VS Code dev containers, Telepresence, Localstack or setting up temporary AWS accounts as a development environment for serverless applications.

Using Docker Compose to run Postgres and any third-party services locally provides a streamlined and consistent development environment. Developers can define services in a docker-compose.yml file, which enables them to configure and launch an entire stack with a single command. In this case, Postgres is encapsulated within a container with predefined configurations. Docker Compose also facilitates easy scaling, updates, and isolation of services, enhancing development efficiency and reducing the setup time for new team members or transitioning between projects. It encapsulates complex configurations, such as Postgres' performance monitoring and logging settings, in a manageable, version-controlled file, simplifying and replicating the service setup across different environments.

“Compose simplifies the control of your entire application stack, making it easy to manage services, networks, and volumes in a single, comprehensible YAML configuration file. Then, with a single command, you create and start all the services from your configuration file.” - Docker documentation

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

Docker,

This foundation now opens the door to even more powerful concepts. You can explore more advanced concepts such as container networking, streamlining the management of complex applications with Docker Compose, and how to make your application data persistent using volumes.

In many projects that are containerized, especially in cases where development is also done locally with docker-compose, teams often have two Dockerfiles, 1 for Development, the other for Production. If you happen to have multiple environments like pre-prod, staging and so on, some teams could have different Dockerfiles for these environments.

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose