15 thoughts on “Docker 20.10 has been released”

  1. I have been waiting many years for

    Support host.docker.internal in dockerd on Linux moby/moby#40007

    No more annoying
    `echo $(ip route show | awk “/default/ {print $ 3}”) host.docker.internal >> /etc/hosts`

    ..when dealing with linux hosts

  2. I am wondering if the upgrade will blow up my existing projects 😛

    Is 20.10.0 a stable release? The 0 minor version


    >Add support for swarm jobs [moby/moby#40307](https://github.com/moby/moby/pull/40307)
    >Add capabilities support to stack/service commands [docker/cli#2687](https://github.com/docker/cli/pull/2687) [docker/cli#2709](https://github.com/docker/cli/pull/2709) [moby/moby#39173](https://github.com/moby/moby/pull/39173) [moby/moby#41249](https://github.com/moby/moby/pull/41249)
    >Add support for sending down service Running and Desired task counts [moby/moby#39231](https://github.com/moby/moby/pull/39231)
    >service: support –mount type=bind,bind-nonrecursive
    >Support ulimits on Swarm services. [moby/moby#41284](https://github.com/moby/moby/pull/41284) [docker/cli#2712](https://github.com/docker/cli/pull/2712)
    >Fixed an issue where service logs could leak goroutines on the worker [moby/moby#40426](https://github.com/moby/moby/pull/40426)


  3. Does anyone know if rootless mode will support networking?

    Say I use traefik for mapping local vhosts to containers. It is my understanding this is only possible if at the minimum the traefik container is running in root mode.

  4. Does this now support use of GPUs from Swarm stacks?

    There was a recent change to docker-compose (and I believe the compose file specification) related to that, but I’m not sure if that’s usable from swarm yet. From the CLI it has been easy for some time using the `–gpus` parameter (with the default runtime) but it was not possible to specify it from a swarm stack definition.

  5. host.docker.internal is now supported on linux

    Just today I was having this fucking issue running a gitlab runner inside docker and I wanted to pull from a gitlab instance on the host machine without connecting both containers to the same network, this is amazing

  6. I woke up to multiple broken servers that run standalone dockerd (no swarm) where the systemd unit simply refuses to start. Even after two reboots. I downgrade to 19.03.14 and my containers are running again. That’s a shame, first time auto upgrades broke my docker.

    Ubuntu 20.04
    “experimental”: true,
    “iptables”: false,
    “live-restore”: true,
    “log-driver”: “json-file”,
    “log-opts”: {
    “max-file”: “3”,
    “max-size”: “10m”
    “metrics-addr”: “[::]:9323”

  7. It broke all my containerd Visual Studio Code projects!

    Docker desktop uninstall (for downgrading) deleted all my containers and images.
    Downloading and installing the older version from their release notes page gave me again the version 3.0.0. Of course only realizing only after building my multi container project downloading. Hence, Downloading the next older version…

    Deleting everything again great to be in home office with an LTE internet connection.
    Lost 4 hours on the end of a 10 hour workday. Such an utter shitshow!

    Forgot to mention:

    * Docker desktop on Mac
    * Isn’t allowed to Mount workspace dir to container

    This also happened on a newly created project out of the Python 3.9 template without any adoptions…


Leave a Comment