Hello, I've been using docker swarm's overlay network with standalone containers attached to it, and when i tried to restart one of them, there is the error that i get : Error response from daemon: Cannot restart container fc: network i7lc22dytdry0dy6kwcq1gfr1 not found

In fact, this command is send to a swarm slave, so the network is created when i run the container, but when i restart it, it stops the container, and remove the network, but it tries to restart the container without recreating the network, as shown here :

Before restart :

root@dockerslave1:~# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
98ce48b3860f        bridge              bridge              local
0442dda5f136        docker_gwbridge     bridge              local
d56fb088b7a5        host                host                local
sof878c2edfc        ingress             overlay             swarm
i7lc22dytdry        network_admin       overlay             swarm
490735057e65        none                null                local

here we have the i7lc22dytdry network, then i do the docker restart on the only container using the network

root@dockerslave1:~# docker restart fc
Error response from daemon: Cannot restart container fc: network i7lc22dytdry0dy6kwcq1gfr1 not found

and then the networks afterwards :

root@dockerslave1:~# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
98ce48b3860f        bridge              bridge              local
0442dda5f136        docker_gwbridge     bridge              local
d56fb088b7a5        host                host                local
sof878c2edfc        ingress             overlay             swarm
490735057e65        none                null                local

Some useful information :

root@dockerslave1:~# docker network inspect network_admin
[
    {
        "Name": "network_admin",
        "Id": "i7lc22dytdry0dy6kwcq1gfr1",
        "Created": "2020-11-29T18:50:01.232786457+01:00",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "10.42.0.0/27",
                    "IPRange": "10.42.0.0/27",
                    "Gateway": "10.42.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": true,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a": {
                "Name": "Shell_admin",
                "EndpointID": "c3ad897c2ada3831721b89535a080424310934c868e011b6c30fe48efacdb2ac",
                "MacAddress": "02:42:0a:2a:00:13",
                "IPv4Address": "10.42.0.19/27",
                "IPv6Address": ""
            },
            "lb-network_admin": {
                "Name": "network_admin-endpoint",
                "EndpointID": "3bb8d18d5ff253de9e748a079c0cf1b575d7fa9b37916774452543f8b8be7d23",
                "MacAddress": "02:42:0a:2a:00:05",
                "IPv4Address": "10.42.0.5/27",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "4097"
        },
        "Labels": {},
        "Peers": [
            {
                "Name": "16e227b94b0e",
                "IP": "10.253.253.254"
            },
            {
                "Name": "a7f617a23256",
                "IP": "10.253.253.2"
            }
        ]
    }
]

root@dockerslave1:~# docker container inspect Shell_admin 
[
    {
        "Id": "091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a",
        "Created": "2020-11-29T17:50:00.952973296Z",
        "Path": "/bin/sh",
        "Args": [
            "-c",
            "bash $@"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 27307,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2020-11-29T17:50:02.553167078Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:35cfd692bb97891422170c381a1d95033f2565d1709fb704434e9411b6ef7e13",
        "ResolvConfPath": "/var/lib/docker/containers/091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a/hostname",
        "HostsPath": "/var/lib/docker/containers/091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a/hosts",
        "LogPath": "/var/lib/docker/containers/091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a/091bc510f1b86dc760de07b8a6091c225b96347576c7c54e76c099f2e159f75a-json.log",
        "Name": "/Shell_admin",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-default",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": null,
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "i7lc22dytdry0dy6kwcq1gfr1",
            "PortBindings": null,
            "RestartPolicy": {
                "Name": "",
                "MaximumRetryCount": 0
            },
            "AutoRemove": true,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": [
                "NET_ADMIN"
            ],
            "CapDrop": null,
            "Capabilities": null,
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 200,
            "Memory": 268435456,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": null,
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": -1,
            "MemorySwappiness": null,
            "OomKillDisable": false,
            "PidsLimit": 20,
            "Ulimits": null,
            "CpuCount": 1,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/ff3eb2b45a8bf877cc7786b1c3002ce1dc5fb0d0ec997a4c53d307f8792fa639-init/diff:/var/lib/docker/overlay2/a5a16f783f10ec5fee6db39c752a603b01d3efbdee411395f1e06a92c51fee44/diff:/var/lib/docker/overlay2/1a219de6631180cbad15e45d1293e502ca109353d3eb7c1cc3816518002bb334/diff:/var/lib/docker/overlay2/b9744248e64b5b43000f9bc575ca504d42abc98a93d88e01513c773f95fb4262/diff",
                "MergedDir": "/var/lib/docker/overlay2/ff3eb2b45a8bf877cc7786b1c3002ce1dc5fb0d0ec997a4c53d307f8792fa639/merged",
                "UpperDir": "/var/lib/docker/overlay2/ff3eb2b45a8bf877cc7786b1c3002ce1dc5fb0d0ec997a4c53d307f8792fa639/diff",
                "WorkDir": "/var/lib/docker/overlay2/ff3eb2b45a8bf877cc7786b1c3002ce1dc5fb0d0ec997a4c53d307f8792fa639/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [],
        "Config": {
            "Hostname": "shell-admin",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": true,
            "OpenStdin": true,
            "StdinOnce": false,
            "Env": [
                "ROOT_PASSWORD=9hyGdEtMFZ",
                "USER_PASSWORD=ADCdtOJ9Nh",
                "CTF_FLAG=CoucouToi",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "DEBIAN_FRONTEND=noninteractive",
                "VERSION=4.9-1"
            ],
            "Cmd": null,
            "Image": "parrotsec/security:latest",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": [
                "/bin/sh",
                "-c",
                "bash $@"
            ],
            "OnBuild": null,
            "Labels": {}
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "dfa33f5dc5fb60cf459befc15a018e49b851a5bd29b25defb19c9fc22269fa72",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/dfa33f5dc5fb",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "network_admin": {
                    "IPAMConfig": {
                        "IPv4Address": "10.42.0.19"
                    },
                    "Links": null,
                    "Aliases": [
                        "091bc510f1b8"
                    ],
                    "NetworkID": "i7lc22dytdry0dy6kwcq1gfr1",
                    "EndpointID": "c3ad897c2ada3831721b89535a080424310934c868e011b6c30fe48efacdb2ac",
                    "Gateway": "",
                    "IPAddress": "10.42.0.19",
                    "IPPrefixLen": 27,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:0a:2a:00:13",
                    "DriverOpts": null
                }
            }
        }
    }
]

In my case, I switched to an ARM template, which isn’t as portable or easy to read.

On Sun, Nov 29, 2020 at 02:52 Pieter [email protected] wrote:

@qmnonic https://github.com/qmnonic I appreciate you bringing this up on this thread again. I'm just coming across this issue right now: I have an application that I have completely prepared for deployment and I have my domain but I would like to get my SSL set up to a permanent public IP but with the current deployment with docker compose and the azure context method, I cannot get specify the vnet/subnet to then use the network gateway.

Do you have another solution/workaround while this is being worked on? (I would love to do this in the CLI but that could be well off) The Azure Portal doesn't seem to have suitable ways to do all of setting up a multi-container instance with docker compose configuration files and specify vnet/subnet.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker/compose-cli/issues/909#issuecomment-735357280, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMU6JWVGYIOJI57WPX25LSSH4SHANCNFSM4TU7RRIA .

@vilhelmprytz You need to:

    sudo dnf config-manager --set-enabled docker-ce-test

Yes, but isn't that the unstable/testing versions of Docker? I just want a stable version 🙂

@vilhelmprytz You need to:

    sudo dnf config-manager --set-enabled docker-ce-test

@qmnonic I appreciate you bringing this up on this thread again. I'm just coming across this issue right now: I have an application that I have completely prepared for deployment and I have my domain but I would like to get my SSL set up to a permanent public IP but with the current deployment with docker compose and the azure context method, I cannot get specify the vnet/subnet to then use the network gateway.

Do you have another solution/workaround while this is being worked on? (I would love to do this in the CLI but that could be well off) The Azure Portal doesn't seem to have suitable ways to do all of setting up a multi-container instance with docker compose configuration files and specify vnet/subnet.

Steps to reproduce the issue:

1. Create ACI Docker context e.g. 'acictx'
2. docker --context acictx run -d -p 12345/udp some-udp-based-network-service-image

Describe the results you received: No errors/warnings, but the public IP address created as part of the ACI container group is using TCP protocol

Describe the results you expected: The public IP address created as part of the ACI container group should use UDP protocol

Additional information you deem important (e.g. issue happens only occasionally): You can verify the protocol used by the IP address with Azure CLI (az container show). Deploying via az container create works as expected (UDP protocol binding is created and communication works).

Tried on Docker Desktop for Mac 2.5.2 (50156). Also tried on Ubuntu Linux with the same effect.

Restarting docker service on swarm manager works for me (workaround).

Same here.

<!-- This issue tracker is for bug reports and feature requests. For questions, and getting help on using docker:

• Docker documentation - https://docs.docker.com
• Docker Forums - https://forums.docker.com
• Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
• Post a question on StackOverflow, using the Docker tag -->

• [x] This is a bug report
• [ ] This is a feature request
• [x ] I searched existing issues before opening this one

<!-- DO NOT report security issues publicly! If you suspect you discovered a security issue, send your report privately to [email protected]. -->

Expected behavior

Actual behavior

The installations fails.

root@stemy:~# apt install docker
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Les paquets supplémentaires suivants seront installés : 
  wmdocker
Les NOUVEAUX paquets suivants seront installés :
  docker wmdocker
0 mis à jour, 2 nouvellement installés, 0 à enlever et 1 non mis à jour.
1 partiellement installés ou enlevés.
Il est nécessaire de prendre 15.3 ko dans les archives.
Après cette opération, 58.4 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [Y/n] 
Réception de :1 http://ftp.debian.org/debian buster/main amd64 wmdocker amd64 1.5-2 [12.8 kB]
Réception de :2 http://ftp.debian.org/debian buster/main amd64 docker all 1.5-2 [2,556 B]
15.3 ko réceptionnés en 0s (42.5 ko/s)
Sélection du paquet wmdocker précédemment désélectionné.
(Lecture de la base de données... 89469 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../wmdocker_1.5-2_amd64.deb ...
Dépaquetage de wmdocker (1.5-2) ...
Sélection du paquet docker précédemment désélectionné.
Préparation du dépaquetage de .../archives/docker_1.5-2_all.deb ...
Dépaquetage de docker (1.5-2) ...
Paramétrage de wmdocker (1.5-2) ...
Paramétrage de docker-ce (5:19.03.13~3-0~debian-buster) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2020-11-29 00:00:57 CET; 9ms ago
     Docs: https://docs.docker.com
  Process: 7703 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 7703 (code=exited, status=1/FAILURE)
dpkg: erreur de traitement du paquet docker-ce (--configure) :
 installed docker-ce package post-installation script subprocess returned error exit status 1
Paramétrage de docker (1.5-2) ...
Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) ...
Des erreurs ont été rencontrées pendant l'exécution :
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@stemy:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-11-29 00:03:20 CET; 3min 56s ago
     Docs: https://docs.docker.com
  Process: 8384 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, 
 Main PID: 8384 (code=exited, status=1/FAILURE)

Nov 29 00:03:18 stemy.me systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 00:03:18 stemy.me systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 29 00:03:18 stemy.me systemd[1]: Failed to start Docker Application Container Engine.
Nov 29 00:03:20 stemy.me systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Nov 29 00:03:20 stemy.me systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Nov 29 00:03:20 stemy.me systemd[1]: Stopped Docker Application Container Engine.
Nov 29 00:03:20 stemy.me systemd[1]: docker.service: Start request repeated too quickly.
Nov 29 00:03:20 stemy.me systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 29 00:03:20 stemy.me systemd[1]: Failed to start Docker Application Container Engine.

Steps to reproduce the behavior

Type sudo apt install docker <!-- Describe the exact steps to reproduce. If possible, provide a minimum reproduction example; take into account that others do not have access to your private images, source code, and environment.

REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED") -->

Output of docker version:

1.5-2

Output of docker info:

root@stemy:~# docker info
Client:
 Debug Mode: false

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Additional environment details (AWS, VirtualBox, physical, etc.) Desktop PC Yunohost 4.0.8.2, based on debian 10.6.

I followed the official installation guide but get this error

Error: Unable to find a match: docker-ce docker-ce-cli

since docker-ce and docker-ce-cli are not present in https://download.docker.com/linux/fedora/33/x86_64/stable/Packages/ (only in https://download.docker.com/linux/fedora/33/x86_64/test/Packages/). Any news on when these packages land in stable?

Was thinking the same. Policy to define travel within the graph is nice, but this should be hidden with higher level vocabulary. inDependecyOrder vs inReverseDependencyOrder would be more readable for the price of an extra nested func call.

I wish we had two functions inDependencyOrder and inReverseDependencyOrder, the traversalConfig is confusing

I found the reason for this , This is due to the HTTP_PROXY configured in the Linux Host. Just added NO proxy for the Registry URL .. It is just worked.

If anyone facing this issue please do the following:

1. Open the file /etc/systemd/system/docker.service.d/http-proxy.conf in VI editor
2. Change or add the lines like below based on your proxy and IP address Environment="HTTP_PROXY=http://proxy.example.com:80/" "NO_PROXY=localhost,127.0.0.1,docker-registry.somecorporation.com"
3. Flush the changes $ sudo systemctl daemon-reload
4. Verify your changes are done.

$ systemctl show --property=Environment docker

1. Restart Docker

$ sudo systemctl restart docker

6 . Restart your Containers/ Registry ... There you go.. Your registry started working... :-)

Thanks, this is very helpful. Should be post in Docker push FAQ

I'll add those on https://github.com/docker/docker.github.io/pull/11794

This is a follow-up proposal for https://github.com/docker/compose-cli/pull/968#issuecomment-735207016

compose up creates/updates resources from compose.yaml definition, but all other commands might not have access to this file (or can't guarantee it has not been edited in the meantime). Resources should be created with metadata (labels) so we can rebuild a partial compose-go model by just inspecting actual resources.

I needed to add a couple of more permissions to get the wordpress example up and running https://github.com/ChiliMonanta/docker-compose-ecs-fargate

ec2:AuthorizeSecurityGroupIngress
ec2:createTags
ec2:RevokeSecurityGroupIngress
ecs:DeleteCluster
ecs:DeleteService
ecs:DeregisterTaskDefinition 
ecs:DescribeClusters
ecs:DescribeServices
ecs:DescribeTasks
ecs:ListTasks
ecs:RegisterTaskDefinition
elasticfilesystem:CreateAccessPoint
elasticfilesystem:CreateFileSystem
elasticfilesystem:CreateMountTarget
elasticfilesystem:DeleteAccessPoint
elasticfilesystem:DeleteMountTarget 
elasticfilesystem:DescribeAccessPoints
elasticfilesystem:DescribeFileSystemPolicy
elasticfilesystem:DescribeFileSystems
elasticfilesystem:DescribeMountTargets
iam:DeleteRolePolicy
iam:GetRolePolicy
iam:ListRoles
iam:PassRole
iam:PutRolePolicy
iam:TagRole
servicediscovery:DeleteNamespace
servicediscovery:TagResource

I suggest (this can come as a follow-up PR) we introduce label com.docker.compose.dependencies to store service dependencies metadata. We for sure can retrieve the compose file with those labels, but this file might have been edited in the meantime. Make sense anyway for compatibility with docker-compose.

IIRC inDependencyOrder relies only on service.GetDependencies so we could have this one support both (labels metadata + read from config file) We could also make a tiny change in docker-compose so it sets this same label, even the down logic would not be updated to limit the effort.

FWIW, this seems to happen only if the tag is latest for some reason:

$ docker manifest create localhost:5000/goreleaser/test_multiarch --amend localhost:5000/goreleaser/test_multiarch:latest-amd64 --amend localhost:5000/goreleaser/test_multiarch:latest-arm64v8 --insecure
Created manifest list localhost:5000/goreleaser/test_multiarch:latest

$ docker manifest push localhost:5000/goreleaser/test_multiarch --insecure
failed to put manifest localhost:5000/goreleaser/test_multiarch:latest: errors:
manifest blob unknown: blob unknown to registry
manifest blob unknown: blob unknown to registry

$ docker manifest create localhost:5000/goreleaser/test_multiarch:foo --amend localhost:5000/goreleaser/test_multiarch:latest-amd64 --amend localhost:5000/goreleaser/test_multiarch:latest-arm64v8 --insecure
Created manifest list localhost:5000/goreleaser/test_multiarch:foo

$ docker manifest push localhost:5000/goreleaser/test_multiarch:foo --insecure
sha256:d58cf5f2b3512a396e5736e152e29a6343bd0c5cda10c3f4862860508f872609

To complete @wilminator answer: the docker container was unable to reach the DNS in my setting, so I added the --network host option, and it worked like a charm.

• To recompile the registry executable, make a directory, change to it, and run this:

docker run --rm -v $(pwd):/mnt --network host -it golang:alpine /bin/sh -c "apk update; apk upgrade; apk add --no-cache bash git openssh;go get github.com/docker/distribution/cmd/registry; mkdir /mnt/bin; cp -pv /go/bin/registry /mnt/bin"

• To build a registry image that works, use this Dockerfile from the directory you created:

FROM registry:latest
COPY ./bin/registry /bin/registry

I then ran

docker build --tag registry:fixed .

and used the registry:fixed image.

Hi I have issues to run the example codes provided in the readme.

Here is the error message.

Here is my modification to adapt to my configuration.

below is my container.

Here is the result after running the codes. It created many network1.

Please help.

@satyajitghana literally read the article right above your comment...

oooh, forgot to mention, i am running Ubuntu 20.04 on WSL2 with kernel 4.19.128-microsoft-standard

@satyajitghana literally read the article right above your comment...

yea got it, 😆 i'm going blind

@satyajitghana literally read the article right above your comment...

In default contexts, perfectly works!! but in awscontext (ECS) I have this Issue

What I did

• allow one-liner to sent progress events
• more homogeneous events for creating, created, ...
• display error status in case of errors

Related issue <!-- If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" -->

<!-- optional tests You can add a / mention to run tests executed by default only on main branch :

• test-aci to run ACI E2E tests
• test-ecs to run ECS E2E tests
• test-windows to run tests & E2E tests on windows --> /test-aci /test-ecs

(not mandatory) A picture of a cute animal, if possible in relation with what you did

https://github.com/docker/distribution/blob/master/reference/normalize.go#L59-L64

Do you really think that sha256 collision is impossible? I know that it is not proven in practice but why to design a flowed a code in the first place?