profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/docker/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Docker docker San Francisco, CA https://www.docker.com Docker provides a simple and powerful developer experience, workflows and collaboration for creating applications.

docker/compose 23411

Define and run multi-container applications with Docker

docker/awesome-compose 12831

Awesome Docker Compose samples

docker/docker-bench-security 7078

The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production.

docker/dockercraft 6416

Docker + Minecraft = Dockercraft

docker/classicswarm 5822

Swarm Classic: a container clustering system. Not to be confused with Docker Swarm which is at https://github.com/docker/swarmkit

docker/docker-py 5402

A Python library for the Docker Engine API

docker/docker-ce 5399

:warning: This repository is deprecated and will be archived (Docker CE itself is NOT deprecated) see the https://github.com/docker/docker-ce/blob/master/README.md :warning:

docker/docker.github.io 3309

Source repo for Docker's Documentation

docker/cli 3030

The Docker CLI

docker/build-push-action 1710

GitHub Action to build and push Docker images with Buildx

issue commentdocker/compose

Feature Request: Provide --quiet option to 'up' command

I'm surprised there is no way to suppress docker-compose messages. It really limits the usefulness of docker-compose run. It's been 3 years.

ulope

comment created time in 20 minutes

issue openeddocker/for-win

Docker desktop versions 4.0.1 to 3.5.1 fail to start on desktop restart.

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Windows software, which we respond to on a best-effort basis.

Support requests in this repository (i.e., trouble installing or using the software) will be ignored, but personalized support is available to Docker Pro and Team customers at https://hub.docker.com/support/desktop/, and community support is available from the Docker community Slack (https://www.docker.com/docker-community).

Issues without sufficient detail to debug them will be closed. They generally need a clear title and description, steps to reproduce, and a diagnostics ID. See https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for how to generate a diagnostics ID either from inside the app or from the command line.


-->

Docker Desktop was not starting up on windows start-up. I've downgraded the versions from 4.0.1 all the way back to 3.5.1 and all these versions have the same error on start-up.

After, I go to Troubleshoot -> Clean/Purge Data -> select WSL 2 -> Delete; Then, the service starts running.

I have to repeat this every time after I start desktop.

<!-- Click these checkboxes after submitting, or place an "x" in them. -->

  • [x] I have tried with the latest version of Docker Desktop
  • [ ] I have tried disabling enabled experimental features
  • [ ] I have uploaded Diagnostics
  • Diagnostics ID: - The screen shows Diagnose failed.

Actual behavior

Docker Desktop service did not start.

Expected behavior

Docker Desktop has to start-up successfully

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible? Yes
  • Is the problem new? Not sure.
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: Microsoft Windows 11 Home Insider Preview - Version - 10.0.22458 Build 22458
  • Docker Desktop Version: 4.0.1 to 3.5.1 (I have not checked older versions). The log files I am attaching are for version 3.5.1
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. Double Click Docker Desktop after windows startup
  2. Dashboard shows error : "Docker Engine Stopped"
  3. Click Troubleshoot-> Clean/Purge Data -> select WSL 2 -> Delete, then go to dashboard:
  4. Service is running.

Log file from <user>\AppData\Local\Docker\log.txt log.txt

created time in an hour

PR closed docker/docker-py

Add network hostname aliases for services.

During a recent project that I worked on I used docker-py to create services in a docker swarm. I stumbled across issue #1571 because my service was not available under the expected hostname. The patch below resolved this for us by allowing to specify aliases.

The patch below obviously would change the API (and probably fail tests). If you're interested in this patch, I'd be happy to rework it appropriately if you could give me some input on how you want handle such an API change.

Signed-off-by: Patrick Bänziger patrick.baenziger@bsi-software.com

+24 -5

5 comments

3 changed files

padyx

pr closed time in an hour

starteddocker/getting-started

started time in an hour

fork smoran09/getting-started

Getting started with Docker

fork in 2 hours

starteddocker/getting-started

started time in 3 hours

starteddocker/getting-started

started time in 3 hours

issue commentdocker/for-mac

Network Errors, Connection Resets, Requiring Docker Restart

I finally got the fcking working solution:

  1. Turn on "Experimental Feature" > "Use the new Virtualization framework"
  2. Edit "/Users/$USER/Library/Group Containers/group.com.docker/settings.json"
  "useVpnkit": false,
  1. Restart Docker Daemon

You can thank me later.

micchickenburger

comment created time in 3 hours

issue commentdocker/for-mac

Networking Fails

@cconnoruk One possible experiment to try: if you switch to the experimental virtualization.framework, then edit ~/Library/Group\ Containers/group.com.docker/settings.json and set useVpnkit to false and restart again, it will use a native kernel networking stack. This can cause problems with VPNs and with Internet Sharing, but assuming those aren't a problem, it uses a more scalable kernel datapath. It would be interesting to hear if the problem still manifests.

Also perhaps take a look at Library/Containers/com.docker.docker/Data/log/vm/console.log when it manifests in case there is an error from Linux itself.

I have tried million of solutions on the Internet. Your solution seems the only truely prevented the issue for me. Although I see the following log message (with virtualization.framework and useVpnkit=false).

[  335.767425] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
cconnoruk

comment created time in 3 hours

fork crazy-max/compose

Define and run multi-container applications with Docker

https://docs.docker.com/compose/

fork in 3 hours

issue commentdocker/for-mac

Network Errors, Connection Resets, Requiring Docker Restart

I ended up working around this issue by using long live connections between my container and host, rather than many short live connections. Specifically I was using an nginx container as a reverse proxy and had the Connection: close header set which essentially prevented socket reuse.

The issue seems to be with the number of sockets that are established, rather than the amount of data transferred.

micchickenburger

comment created time in 3 hours

issue commentdocker/for-mac

Network Errors, Connection Resets, Requiring Docker Restart

I can confirm that Docker Engine 20.10.8 is still having this issue. Containers cannot reach host's network if one of the them sent lots network packets.

micchickenburger

comment created time in 3 hours

issue openeddocker/docker-bench-security

Exit Code Control, and Output Format Options

Hey all, this is part question and part suggestion.

When running Docker-Bench as part of a CI (in particular, running it from the Docker container method), shouldn't the execution exit with a non-zero code if there are any 'notes' or at least 'warnings'?

Additionally, I would like to be able to control the exit (ie. only exit 1 if there are warnings, for example). Either this, or being able to control a "pass" or "fail" as part of CI if the returned score is +/- a certain value.

Further, is there a way to include output options in specific formats (ie. JUnit, XML, SARIF, etc.), so that it is more easily consumed by CI/CD tools?

created time in 3 hours

issue openeddocker/for-linux

Support for Ubuntu 21.10 Impish Indri

Please add support for Ubuntu 21.10. It will be release on October 14.

Also see #940 and #832. I'm opening the new issue because the first one seems a bit stale.

Thanks.

created time in 3 hours

issue commentdocker/compose

Docker-compose created container cannot access Internet

This issue has been automatically marked as not stale anymore due to the recent activity.

payalord

comment created time in 4 hours

issue commentdocker/compose

Docker-compose created container cannot access Internet

I think this still exists, but it is really hard to reproduce. If someone else comes across this, please send in-depth reproduction steps (Unlike me 6 months ago)

payalord

comment created time in 4 hours

starteddocker/dockercraft

started time in 4 hours

IssuesEvent

issue commentdocker/buildx

fail to resolve address (it works on master)

I'm running the buildkitd image manually as priviliged, I've also set the seccomp profile to unconfined, but it keeps failing with the same error. Is there a workaround?

aojea

comment created time in 4 hours

starteddocker/awesome-compose

started time in 4 hours

issue closeddocker/compose

The project starts with docker compose image. Some files need to be mounted to the host to modify the configuration. The volumes attribute is used

The project starts with docker compose image. Some files need to be mounted to the host to modify the configuration. The volumes attribute is used

volumes:

  • "./docker/dev/WEB-INF:/usr/local/tomcat/webapps/cas/WEB-INF"

The front is the host directory, and the back is the directory in the container. After startup, the host directory can be created, but there is nothing under this path in the container. If it is deleted, it can be started and accessed normally without volumes.

All kinds of God, help, please advise, docker novice

closed time in 4 hours

wenming5112

issue closeddocker/compose

Network priority ignored for external networks

Not sure if this is intended behaviour or a bug.

I have a docker-compose file for an OpenVPN container which uses two external networks:

networks:
  astnet:
    external: true
    name: astnet
  ovpnnet:
    external: true
    name: ovpnnet
services:
  openvpn:
    ... left out intentionally ...
    networks:
      astnet:
        ipv4_address: 192.168.250.250
      ovpnnet:
        ipv4_address: 192.168.252.2
    ports:
    - 192.168.253.2:1194:1194/udp
    - 192.168.253.2:1195:1194/udp
version: '2.4'

The started container uses astnet for the default route:

bash-4.3# ip route
default via 192.168.250.1 dev eth0 
10.0.2.0/24 dev tun0 proto kernel scope link src 10.0.2.1 
192.168.3.0/24 via 10.0.2.2 dev tun0 
192.168.250.0/24 dev eth0 proto kernel scope link src 192.168.250.250 
192.168.252.0/24 dev eth1 proto kernel scope link src 192.168.252.2

and also in the matching iptables rule:

Chain DOCKER (24 references)
target     prot opt source               destination      
ACCEPT     udp  --  anywhere             192.168.250.250      udp dpt:openvpn

Now I would like to configure docker to use the ovpnet as default network. According to https://docs.docker.com/compose/compose-file/compose-file-v2/#priority and Issue #4645 it should be possible by setting a priority like this:

      astnet:
        ipv4_address: '192.168.250.250'
        priority: 200
      ovpnnet:
        ipv4_address: '192.168.252.2'
        priority: 300

But this doesn't change anything. astnet is still eth0 and has the default route. I also tried switching the priorities and changing the order of the networks but no success.

Version informations

docker version:

Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:05 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:19:41 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

docker-compose version:

docker-compose version 1.24.1, build 4667896b
docker-py version: 3.7.3
CPython version: 3.6.8
OpenSSL version: OpenSSL 1.1.0j  20 Nov 2018

closed time in 4 hours

pytz

issue closeddocker/compose

Setting PYTHONDEVMODE environment variables causes seg fault

Description of the issue

As a Python developer, I had the $PYTHONDEVMODE environment variable set in my shell to help me detect deprecations and resource leaks. I updated by docker installation and docker-compose started to fail due to the python memory debug support added in Python 3.6 (ref: [What's New in Python 3.6])(https://docs.python.org/3.6/whatsnew/3.6.html#pythonmalloc-environment-variable).

$
$
$ /usr/local/bin/docker-compose version
docker-compose version 1.28.5, build c4eb3a1f
docker-py version: 4.4.4
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020
$
$
$
$ PYTHONDEVMODE=1 /usr/local/bin/docker-compose version
Debug memory block at address p=0x7ff63d606690: API '�'
    15987178197214944733 bytes originally requested
    The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfd):
        at p-7: 0xdd *** OUCH
        at p-6: 0xdd *** OUCH
        at p-5: 0xdd *** OUCH
        at p-4: 0x72 *** OUCH
        at p-3: 0x00 *** OUCH
        at p-2: 0x7c *** OUCH
        at p-1: 0x00 *** OUCH
    Because memory is corrupted at the start, the count of bytes requested
       may be bogus, and checking the trailing pad bytes may segfault.
    The 8 pad bytes at tail=0xddde5dd41b3e446d are zsh: segmentation fault  PYTHONDEVMODE=1 /usr/local/bin/docker-compose version
$
$
$

Context information (for bug reports)

The following output is with the PYTHONDEVMODE environment variable unset.

Output of docker-compose version

docker-compose version 1.28.5, build c4eb3a1f
docker-py version: 4.4.4
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020

Output of docker version

Client: Docker Engine - Community
 Version:           20.10.5
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        55c4c88
 Built:             Tue Mar  2 20:13:00 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.5
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       363e9a8
  Built:            Tue Mar  2 20:15:47 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker-compose config

Not relevant since it happens regardless of the docker-compose configuration.

Steps to reproduce the issue

  1. export PYTHONDEVMODE=1 in your shell
  2. run docker-compose version

Observed result

Debug memory block at address p=0x7ff63d606690: API '�'
    15987178197214944733 bytes originally requested
    The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfd):
        at p-7: 0xdd *** OUCH
        at p-6: 0xdd *** OUCH
        at p-5: 0xdd *** OUCH
        at p-4: 0x72 *** OUCH
        at p-3: 0x00 *** OUCH
        at p-2: 0x7c *** OUCH
        at p-1: 0x00 *** OUCH
    Because memory is corrupted at the start, the count of bytes requested
       may be bogus, and checking the trailing pad bytes may segfault.
    The 8 pad bytes at tail=0xddde5dd41b3e446d are zsh: segmentation fault  PYTHONDEVMODE=1 /usr/local/bin/docker-compose version

Expected result

docker-compose version 1.28.5, build c4eb3a1f
docker-py version: 4.4.4
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020

Stacktrace / full error message

Debug memory block at address p=0x7ff63d606690: API '�'
    15987178197214944733 bytes originally requested
    The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfd):
        at p-7: 0xdd *** OUCH
        at p-6: 0xdd *** OUCH
        at p-5: 0xdd *** OUCH
        at p-4: 0x72 *** OUCH
        at p-3: 0x00 *** OUCH
        at p-2: 0x7c *** OUCH
        at p-1: 0x00 *** OUCH
    Because memory is corrupted at the start, the count of bytes requested
       may be bogus, and checking the trailing pad bytes may segfault.
    The 8 pad bytes at tail=0xddde5dd41b3e446d are zsh: segmentation fault  PYTHONDEVMODE=1 /usr/local/bin/docker-compose version

Additional information

OS version / distribution, docker-compose install method, etc.

  • macOS Catalina, version 10.15.7
  • MacBook Pro (15-inch, 2019)
  • installed as part of docker desktop version 3.2.1
    • Engine: 20.10.5
    • Compose: 1.28.5
    • Kubernetes: 1.19.7
    • Notary: 0.6.1
    • Credential Helper: 0.6.3
    • Snyk:: 1.432.0

closed time in 4 hours

dave-shawley

issue closeddocker/compose

docker-compose cli output broken in Git-Bash

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Windows software, which we respond to on a best-effort basis.

Support requests in this repository (i.e., trouble installing or using the software) will be ignored, but personalized support is available to Docker Pro and Team customers at https://hub.docker.com/support/desktop/, and community support is available from the Docker community Slack (https://www.docker.com/docker-community).

Issues without a clear title, description, and diagnostics ID cannot be debugged, and will be closed. See https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for how to generate a diagnostics ID either from inside the app or from the command line.


-->

<!-- Click these checkboxes after submitting, or place an "x" in them. -->

  • [x] I have tried with the latest version of Docker Desktop
  • [x] I have tried disabling enabled experimental features
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: C519CC2A-7347-4ABB-863D-A2D282655B16/20210306164223

Actual behavior

On $ docker-compose pull, the println output for progress bars is not "merged" on Git-Bash (Git for Windows 2.30.1). Starting with Docker 3.2.0 and 3.2.1: image

Expected behavior

Same output as with Docker 3.1.0: grafik

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: Windows 10 Pro 2004, Build 19041.804
  • Docker Desktop Version: 3.2.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No.

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

1. Take sample compose file from https://docs.docker.com/compose/compose-file/compose-file-v3/
2. Save as test.yml
3. $ docker-compose -f test.yml pull

closed time in 4 hours

fkluthe

issue closeddocker/compose

Compose treats file as directory when using a remote docker daemon

<!-- Welcome to the docker-compose issue tracker! Before creating an issue, please heed the following:

  1. This tracker should only be used to report bugs and request features / enhancements to docker-compose
    • For questions and general support, use https://forums.docker.com
    • For documentation issues, use https://github.com/docker/docker.github.io
    • For issues with the docker stack commands and the version 3 of the Compose file, use https://github.com/docker/cli
  2. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
  3. When making a bug report, make sure you provide all required information. The easier it is for maintainers to reproduce, the faster it'll be fixed. -->

Description of the issue

When using a remote docker daemon, compose treats file as directory, leading to failure in building container. No such problem when using a local daemon.

Context information (for bug reports)

docker-compose.yml

version: '3'
services:
    web:
        build:
            context: ./docker/nginx
        ports:
            - "8888:80"
        volumes:
            - ./docker/nginx/symfony.conf:/etc/nginx/conf.d/default.conf

./docker/nginx/symfony.conf

server {
    listen 80;
    server_name web;
    root /var/www/myapp/www;

    location / {
        # try to serve file directly, fallback to index.php
        try_files $uri /index.php$is_args$args;
    }

    location ~ ^/index\.php(/|$) {
        #fastcgi_pass unix:/var/run/php7.2-fpm.sock;
        fastcgi_pass php:9000;
        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
        fastcgi_buffer_size 128k;
        fastcgi_buffers 4 256k;
        fastcgi_busy_buffers_size 256k;
        internal;
    }

    location ~ \.php$ {
        return 404;
    }

    error_log /var/log/nginx/project_error.log;
    access_log /var/log/nginx/project_access.log;
}

Shell Variables

DOCKER_HOST=tcp://192.168.1.1:2376
DOCKER_TLS_VERIFY=1

Output of docker-compose version

docker-compose version 1.26.2, build eefe0d31
docker-py version: 4.2.2
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020

Output of docker version

Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:41:33 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:44:21 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Steps to reproduce the issue

  1. setup a remote docker daemon
  2. create docker-compose file along with symfony.conf file
  3. docker-compose up --build -d

Observed result

Error, not building container, stack down

Expected result

stack up, container built

Stacktrace / full error message

Recreating 5c4df28e297f_atlas-contrib_web_1 ... error

ERROR: for 5c4df28e297f_atlas-contrib_web_1  Cannot start service web: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/Users/myself/Sites/myapp/docker/nginx/symfony.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/dd9cbb1e25c6f2b29ffebc3dd18e0709acec8d78d858d3676f0ff12bebb038cc/merged\\\" at \\\"/var/lib/docker/overlay2/dd9cbb1e25c6f2b29ffebc3dd18e0709acec8d78d858d3676f0ff12bebb038cc/merged/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for web  Cannot start service web: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/Users/myself/Sites/myapp/docker/nginx/symfony.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/dd9cbb1e25c6f2b29ffebc3dd18e0709acec8d78d858d3676f0ff12bebb038cc/merged\\\" at \\\"/var/lib/docker/overlay2/dd9cbb1e25c6f2b29ffebc3dd18e0709acec8d78d858d3676f0ff12bebb038cc/merged/etc/nginx/conf.d/default.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

Additional information

Docker daemon host: debian 10, latest version Docker client host: mac os 10.15.6

closed time in 4 hours

titiyoyo

issue commentdocker/compose

The project starts with docker compose image. Some files need to be mounted to the host to modify the configuration. The volumes attribute is used

This issue has been automatically closed because it had not recent activity during the stale period.

wenming5112

comment created time in 4 hours

issue commentdocker/compose

Network priority ignored for external networks

This issue has been automatically closed because it had not recent activity during the stale period.

pytz

comment created time in 4 hours