3 ms·
I know I was just downvoted for answering your questions before, but I thought I'd reply here just to share what I've hit so far during today's work day using D
by cookiecaper 10y ago
I know I was just downvoted for answering your questions before, but I thought I'd reply here just to share what I've hit so far during today's work day using Docker. Just today.
1. `docker push` fails because of a mysteriously-vanished cache layer, forcing `docker build --no-cache` to work.
2. `docker-compose stop [service]` broke in a weird way, failing to detect the service's stoppage, creating a duplicate service of the same name that I couldn't do anything with. Had to clear out the duplicate container with `docker rm -fv ...` and now trying to figure out how to make `docker-compose` happy again.
These are totally normal, conventional operations that should not be choking for unexplained reasons.
And people suggest running production workloads on this, for some reason.
and bonus:
3. Tried the `docker build --squash` feature suggested by another commenter, to find it requires "experimental support" to be enabled in the Docker daemon. I have enough problems with docker without that, so I'm going to pass.