Docker images vanish when using user namespaces

This is with reference to https://github.com/docker/docker/issues/20827. But, that thread is already closed and is not getting traction. Can we open that thread or discuss the issue here?

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

First, the remap didn't work.
I ensured to touch the files before issuing remap command.
# docker version
Client:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 16:16:33 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 16:16:33 2016
 OS/Arch:      linux/amd64

#cat /etc/os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.2 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.2"

#uname -r
3.10.0-229.el7.x86_64

# ls -l /etc/subuid /etc/subgid
-rw-r--r--. 1 root root 0 Mar  8 23:11 /etc/subgid
-rw-r--r--. 1 root root 0 Mar  8 23:11 /etc/subuid

#getent passwd dockremap
No output

#getent group dockremap
No output

# docker daemon -D --userns-remap=default
DEBU[0000] docker group found. gid: 499
DEBU[0000] Server created for HTTP on unix (/var/run/docker.sock)
INFO[0000] User namespaces: ID ranges will be mapped to subuid/subgid ranges of: dockremap:dockremap
FATA[0000] Error starting daemon: Can't create ID mappings: No subuid ranges found for user "dockremap"

Any pointers?
Then, I manually created subuid and subgid entries like below and then why I start the docker daemon, all the docker images vanish from my system and I keep getting below errors:
# cat /etc/subuid
dockremap:20000:10000
# cat /etc/subgid
dockremap:20000:10000

# docker daemon --userns-remap=default
INFO[0000] User namespaces: ID ranges will be mapped to subuid/subgid ranges of: dockremap:dockremap
WARN[0000] devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.
INFO[0000] devmapper: Creating filesystem xfs on device docker-253:1-202869472-base
INFO[0001] devmapper: Successfully created filesystem xfs on device docker-253:1-202869472-base
INFO[0001] Graph migration to content-addressability took 0.00 seconds
INFO[0001] Firewalld running: false
INFO[0001] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
INFO[0001] Loading containers: start.

INFO[0001] Loading containers: done.
INFO[0001] Daemon has completed initialization
INFO[0001] Docker daemon                                 commit=c3959b1 execdriver=native-0.2 graphdriver=devicemapper version=1.10.2
INFO[0001] API listen on /var/run/docker.sock
ERRO[0001] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0001] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0002] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0002] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0002] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0002] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0002] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0002] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0002] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0002] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0003] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0003] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0003] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0003] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0003] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0003] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0004] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0004] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0004] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0004] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0004] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0004] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0005] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0005] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0005] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0005] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0005] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0005] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0006] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0006] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0006] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0006] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0006] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0006] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0007] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0007] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0007] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0007] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0007] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0007] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0007] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0007] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0008] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0008] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0008] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0008] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0008] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0008] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0009] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0009] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0009] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0009] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0009] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0009] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0010] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0010] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0010] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0010] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0010] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0010] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0010] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0010] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0011] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0011] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0011] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0011] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0011] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0011] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0012] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0012] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0012] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0012] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0012] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0012] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0013] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0013] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0013] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0013] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0013] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0013] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0013] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0013] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0014] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0014] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0014] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0014] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0014] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0014] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0015] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0015] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0015] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0015] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0015] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0015] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0016] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0016] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0016] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0016] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0016] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0016] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0017] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0017] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0017] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0017] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0017] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0017] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0017] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0017] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0018] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0018] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0018] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0018] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0018] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0018] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0019] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0019] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0019] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0019] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0019] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0019] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0019] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0019] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0020] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0020] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0020] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0020] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0020] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0020] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0021] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0021] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0021] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0021] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0021] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0021] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0021] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0021] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0022] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0022] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0022] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0022] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0022] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0022] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0023] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0023] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0023] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0023] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0023] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0023] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0024] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0024] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0024] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0024] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0024] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0024] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0025] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0025] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0025] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0025] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0025] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0025] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0026] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0026] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0026] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0026] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0026] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0026] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0027] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0027] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0027] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0027] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0027] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0027] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0027] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0027] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0028] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0028] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0028] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0028] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0028] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0028] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0029] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0029] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0029] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0029] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0029] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0029] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0029] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0029] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0030] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0030] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0030] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0030] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0030] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0030] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0031] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0031] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0031] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0031] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0031] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0031] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0031] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0031] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0032] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0032] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0032] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0032] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0032] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0032] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0033] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0033] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0033] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0033] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0033] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0033] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0034] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0034] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0034] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0034] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0034] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0034] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0035] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0035] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0035] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0035] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0035] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0035] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0036] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0036] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0036] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0036] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0036] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0036] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0037] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0037] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0037] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0037] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0037] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0037] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0037] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0037] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0038] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0038] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0038] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0038] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0038] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0038] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0039] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0039] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0039] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0039] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0039] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0039] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0040] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0040] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0040] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0040] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0040] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0040] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0040] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0040] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0041] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0041] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0041] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0041] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0041] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0041] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0042] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0042] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0042] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0042] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0042] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0042] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0042] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0042] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0043] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0043] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0043] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0043] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0043] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0043] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0044] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0044] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0044] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0044] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0044] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0044] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0045] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0045] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0045] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0045] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0045] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0045] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0046] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0046] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0046] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0046] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0046] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0046] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0046] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0046] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0047] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0047] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0047] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0047] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0047] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0047] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0048] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0048] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0048] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0048] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0048] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0048] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0049] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0049] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0049] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0049] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0049] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0049] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0049] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0049] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0050] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0050] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0050] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0050] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0050] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0050] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0051] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0051] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0051] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0051] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0051] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0051] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0051] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0051] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0052] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0052] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0052] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0052] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0052] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0052] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0053] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0053] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0053] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0053] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0053] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0053] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0054] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0054] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0054] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0054] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0054] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0054] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0055] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0055] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0055] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0055] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0055] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0055] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0056] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0056] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0056] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0056] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0056] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0056] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0057] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0057] Handler for GET /v1.22/images/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such image: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a
ERRO[0057] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0057] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0057] Handler for GET /v1.22/containers/7c09415c3462/json returned error: No such container: 7c09415c3462
ERRO[0057] Handler for GET /v1.22/images/7c09415c3462/json returned error: No such image: 7c09415c3462
ERRO[0057] Handler for GET /v1.22/containers/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such container: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0057] Handler for GET /v1.22/images/54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1/json returned error: No such image: 54d5b87c189cfc3ba545f43cf007156d4bade35177451b611f6ff4e2d0fdf0a1
ERRO[0058] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0058] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0058] Handler for GET /v1.22/containers/54d5b87c189c/json returned error: No such container: 54d5b87c189c
ERRO[0058] Handler for GET /v1.22/images/54d5b87c189c/json returned error: No such image: 54d5b87c189c
ERRO[0058] Handler for GET /v1.22/containers/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such container: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0058] Handler for GET /v1.22/images/73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831/json returned error: No such image: 73e2d3e1250f3120b2f11f7b2691cc4bf86ebbb798f018100f4437a1b61ec831
ERRO[0059] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0059] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0059] Handler for GET /v1.22/containers/73e2d3e1250f/json returned error: No such container: 73e2d3e1250f
ERRO[0059] Handler for GET /v1.22/images/73e2d3e1250f/json returned error: No such image: 73e2d3e1250f
ERRO[0059] Handler for GET /v1.22/containers/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such container: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0059] Handler for GET /v1.22/images/282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327/json returned error: No such image: 282e0274e88c66763a54bff439952b0152a8ee94b957380e6e4c3695420fd327
ERRO[0060] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0060] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0060] Handler for GET /v1.22/containers/282e0274e88c/json returned error: No such container: 282e0274e88c
ERRO[0060] Handler for GET /v1.22/images/282e0274e88c/json returned error: No such image: 282e0274e88c
ERRO[0060] Handler for GET /v1.22/containers/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such container: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0060] Handler for GET /v1.22/images/32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28/json returned error: No such image: 32ff50af2de2470f77b87d02579d8f457866ef25d6df7e1fed519004fc3b0c28
ERRO[0060] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0060] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0061] Handler for GET /v1.22/containers/32ff50af2de2/json returned error: No such container: 32ff50af2de2
ERRO[0061] Handler for GET /v1.22/images/32ff50af2de2/json returned error: No such image: 32ff50af2de2
ERRO[0061] Handler for GET /v1.22/containers/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such container: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0061] Handler for GET /v1.22/images/c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442/json returned error: No such image: c217f7f0252f2804288bc6d3d0513e6305e261611945b25dce82cfceedfca442
ERRO[0061] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0061] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0061] Handler for GET /v1.22/containers/c217f7f0252f/json returned error: No such container: c217f7f0252f
ERRO[0061] Handler for GET /v1.22/images/c217f7f0252f/json returned error: No such image: c217f7f0252f
ERRO[0062] Handler for GET /v1.22/containers/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such container: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0062] Handler for GET /v1.22/images/6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a/json returned error: No such image: 6afe59fb900dcd63b39f71d1c5d2250c5d81d69ea0abe701d9860243fc86461a
ERRO[0062] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0062] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0062] Handler for GET /v1.22/containers/6afe59fb900d/json returned error: No such container: 6afe59fb900d
ERRO[0062] Handler for GET /v1.22/images/6afe59fb900d/json returned error: No such image: 6afe59fb900d
ERRO[0063] Handler for GET /v1.22/containers/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such container: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0063] Handler for GET /v1.22/images/499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179/json returned error: No such image: 499a8df18712664ee2b79befc0aaf93964fbb861cf9956585db7c2c717057179
ERRO[0063] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0063] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0063] Handler for GET /v1.22/containers/499a8df18712/json returned error: No such container: 499a8df18712
ERRO[0063] Handler for GET /v1.22/images/499a8df18712/json returned error: No such image: 499a8df18712
ERRO[0064] Handler for GET /v1.22/containers/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such container: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0064] Handler for GET /v1.22/images/de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a/json returned error: No such image: de861b2759bfc856a1e33cbf70eb0072f5b7522d3ff5a921d4c026796ebc4f6a
ERRO[0064] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0064] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0064] Handler for GET /v1.22/containers/de861b2759bf/json returned error: No such container: de861b2759bf
ERRO[0064] Handler for GET /v1.22/images/de861b2759bf/json returned error: No such image: de861b2759bf
ERRO[0065] Handler for GET /v1.22/containers/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such container: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0065] Handler for GET /v1.22/images/5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44/json returned error: No such image: 5174ad448df8826eb79308783a662b5642b6192520ef2d1c700f881b981d1c44
ERRO[0065] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0065] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0065] Handler for GET /v1.22/containers/5174ad448df8/json returned error: No such container: 5174ad448df8
ERRO[0065] Handler for GET /v1.22/images/5174ad448df8/json returned error: No such image: 5174ad448df8
ERRO[0066] Handler for GET /v1.22/containers/7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a/json returned error: No such container: 7c09415c3462d932718567a53aa762121a27813efc9a7d4532e83c372ef5672a

Did we test this on Red Hat 7.2?

/cc @estesp

There are two issues here--one is that RHEL7/CentOS7 don't manage /etc/sub{u,g}id files properly so they must be self-managed as you found.  This is a distro currency issue, and not much we can do other than output the error message you saw about the fact that the remapping user has no ranges defined in the subordinate ID files.
Secondly, it looks like you have a tool which immediately connected to the Docker daemon to try and look up images and containers on the daemon?  Because of the restriction mentioned in the note on user namespace enablement at the daemon level (https://docs.docker.com/engine/reference/commandline/daemon/#daemon-user-namespace-options) you will see that layers of images/containers are separate local caches for user namespaces "on" vs. user namespaces "off".  Your images and containers for running in non-user namespace'd mode are still there, and if you restart the daemon without --userns-remap they will all be visible again.
Because we have to have shift file ownership for the user namespace remapping case to the uid/gid ranges found in the subordinate ID files, you must re-pull docker images and start new containers after the first time you start the daemon with user namespaces enabled, as those layers will now have the proper ownership for your remapped uid/gid range that are valid inside the container process.
We can make this clearer in the docs; this blog post (disclosure: I wrote it) explains is best in the paragraph towards the end beginning with "Important note"--with the caveat we no longer migrate your "root-owned" content to the "0.0" subdir.

I think we can add a note to the documentation, explaining that "userns" and "non-userns" storage is kept separate. I'll label this a "docs" issue

I'm a beginner looking to get some first hand experience working in FOSS projects. For this issue, is the small documentation change all that is required? If so I'd like to give it a try.

@dustinlapierre awesome! The markdown file to generate that part of the documentation can be found in this repository; https://github.com/docker/docker/blob/master/docs/reference/commandline/daemon.md#daemon-user-namespace-options, and you can find the workflow and many other tips in our contributors guide; https://docs.docker.com/opensource/project/who-written-for/

Which is the file that this refers to?  When I fork the docs, I have this path:
docker/docs/reference/commandline
But I cannot find any daemon.md file?

@gamesbook the file is now called dockerd.md, because the daemon and client will be a separate binaries in docker 1.12. Thanks for helping out!

I'm looking to get my feet wet in contributing - perhaps this is something I could look at?
It seems that the pull request to fix this was rejected, but I'm sure I can finish it off if this is still a problem.

@lewisdaly that would be awesome! Having a note in the reference docs would be a good start; however, the section on user namespaces is quite lengthy for inside the "reference" docs itself, and maybe we should consider moving it to its own page in another section of the documentation (we should keep a short introduction, and link to the dedicated page).
Let us know if you would be interested to work on that as well; @mstanleyjones may be better able to tell what's needed for that change
(FWIW, I noticed there's also a short introduction article about user namespaces on success.docker.com)

Great - I'll look into it!
#dibs

@mstanleyjones I've added a note in docs/reference/commandline/dockerd.md. I'm keen to help move the namespace section to another part of the documentation as @thaJeztah suggested.
Are you able to point me in the right direction? I figure I should wait to make a PR for this until I have put the necessary link in that points to wherever we will move the namespace docs to - unless it's worth closing off this issue first?
Cheers!

Hi @lewisdaly, and thanks for your offer to help. I think perhaps a good first run at this would be to add a section to https://docs.docker.com/engine/admin/, which talks about how to configure and run the Docker daemon.  If I were going to write a topic about this, it might include why you would use namespaces, how to configure namespaces in general, and a specific example of configuring a namespace. The Markdown file that represents the above link is: https://github.com/docker/docker.github.io/blob/master/engine/admin/index.md
Please let me know if I can help and I'd be happy to review your content!

Thanks @mstanleyjones , I'll start working on it.
I've opened a new ticket in the documentation repo here. Once we get those changes in, I'll make a link to that documentation to tidy up the user namespace section in the reference docs as @thaJeztah suggested.

Just a related question, once I set user namespace in docker can I remove all the folder from /var/lib/docker/ apart from the new mapping one (uid.gid) ?
Because I think I have a lot of images in it that won't be used anymore (if needed they will be downloaded again) and takes a lot of space.

@Darkheir yes, that should be fine.  I would probably shut the daemon down before doing that but it shouldn't be strictly necessary (if you're already running with --userns-remap then your daemon shouldn't have any files open outside of the uid.gid directory).

Ok, thank you !


Future after 17th March 2024

Since Azure is discontinuing support for php for their libraries, what is the plan for then on?

To be clear i am not asking out of entitlement, I would like to help write if someone experience can guide me around the pitfalls

This adapter becomes deprecated. If somebody wants to spend the time, they can implement the REST. API to make the same calls, and publish an adapter as a standalone package.

Is not easier to covert this package, since there are subscribers who already use this package?

Sure it's easier for the users but not for me. I don't want to maintains an Azure SDK and I don't want to rely on young or poorly maintained community packages.

Wait you maintain the entire flysystem packages alone? like a million people use it, and it's just one person maintaining it?

You'd be surprised how few people actually maintain all of the PHP open source packages that literally everybody uses. So, yeah, it's just me 😅

I don't know if i am good in php, but I have been using laravel for a long time and its is the only framework i am good at in many ways. I would like to help out but not sure if i know how

@frankdejonge I know you mentioned not wanting to rely on young or poorly maintained packages, can you quantify that a bit more? For example, not sure if you've seen https://github.com/Azure-OSS/azure-storage-php
It appears to be ~6 months old, the namespace looks generic enough, and appears to be moving in the right direction. So I'm just curious if this actually looks promising enough to use in the future? or if it's not yet at the point where you'd want to leverage.

@natewiebe13 looks promising, and Pim is a reputable OSS contributor. It seems like a one person show though, which can be risky as they might switch jobs and not be on azure anymore. I'll see if I can reach out and see what's what.

As for quantifying maintenance and reputation, if somebody figured figured that out, let me know. I spend my free time maintaining this stuff so it's a personal investment for me.


Implement conditional encoding/drawing based on per-stream tags

If the frame doesn't have a specified tag, the frame doesn't pass to the encoder. Similarly, if the frame doesn't have a specified tag (other than the encoding tag), the draw element skips it.
The feature can lead to generating of 'sparse' video streams which are partially filled with frames (e.g. only key-frames are configured with tags).
Why it is required?
We may need to debug and visualize only certain streams; for the others, we don't want to encode and draw to save resources. To implement that, we may use a custom source/transit adapter, which injects additional tags into streams that must be encoded and visualized.
Similarly, only when something useful occurs in the stream a pyfunc may be utilized, which will inject a required tag causing the frames to be drawn and encoded to the output. If there is no valuable information within the frame, it is not drawn or encoded.

NB. to document: iframeinterval


Allow to configure uvicorn logging

Trying to add custom handlers to the application logger we have found that the uvicorn ones are not working as expected. It seems that uvicorn overrides the logging configuration when the Config object is initialized.
It would be nice to allow users to configure the uvicorn logger. This can be done by setting the path to a registry configuration file when creating uvicorn's Config object.

A PR has been added with a proposal to solve this issue but it may not be the best solution. It is open to other proposals.


Fractional seconds support

I did not found the way to read values to SysTime type. There is only DateTime conversion but it doesn't support fractional seconds.
Only mention to fractional seconds in code is here: https://github.com/mysql-d/mysql-native/blob/469f9c6cc66eadd5fc306a6a184aa1a49087167c/source/mysql/protocol/packet_helpers.d#L46
which states, that MySql doesn't store it, but it is not true with v5.6 and newer as described in: https://dev.mysql.com/doc/refman/5.7/en/date-and-time-type-overview.html (was with 5.5)

@Abscissa sorry to bug you, but was this added?

@Abscissa sorry to bug you, but was this added?


[4.6.0] Uncaught Error: Specified filePath does not exist

Describe the bug
Error is thrown when using mjml 4.6.0
To Reproduce
Steps to reproduce the behavior:

Create a file with this MJML code: <mjml>...</mjml>
Render it to HTML by doing 'mjml2html(mjml)'
See error

Expected behavior
No errors are thrown
MJML environment (please complete the following information):

OS: WIN10
MJML Version 4.6.0

Additional context
It seems like filePath always defaults to '.' instead of null/undefined. overriding the filePath option fixes the error:
mjml2html(mjml, {
    filePath: null
})

ah, its probably due to me trying to run mjml in the browser by mocking out fs/uglify.js (which works with 4.5.x)
relevant code: https://github.com/mjmlio/mjml/blob/master/packages/mjml-parser-xml/src/index.js#L50

@DRoet maybe, i can't reproduce the issue with a simple node script
We indeed made a few changes on this file, now filePath is checked using fs to know if it's a file or directory

@kmcb777 ,  i do experience the same file not found error after upgrading to 4.6.0.  Seems that the way mjml interpret filepath is different from the previous version.

Can you provide more info about that please @fireworks2005 ?

@fireworks2005 This error was happening when none of the --config options were used in the cli.
This should be already fixed in the latest release 👍
I still couldn't reproduce when importing mjml in code and using mjml2html()
Did you have the error when using it like this, or with the cli ?

@kmcb777 , i am good now. i dont see any error with the latest version

It seems ok for everyone now so i think we can close this one 👍

i have the same error, and resoved by override filePath, I'm not sure if there are other effects
mjml2html(mjml, {     filePath: null })


enrollment with csr

Reason for this PR

The user wants to setup a SECURE connection and not have the system generate and send him his private key

Changes in this PR

Extend the enrollment to receive a csr
Add a new test where a user is enrolled with his CSR

Still missing: Extended Test to have the user access the chain with their own private key

Further Work is required:
https://github.com/upb-uc4/hlf-api/issues/44
https://github.com/upb-uc4/hlf-api/issues/46


Black screen when extending A-Frame hit-test-example with AR.js marker detection

Do you want to request a feature or report a bug?
Report a bug.

What is the current behavior?
I would like to extend a project I found on glitch, which includes an example of a-frame and hit-testing
Link to the original Example: https://glitch.com/~ar-starter-kit
The example itself works great but when I add a script tag to import aframe-ar.js and press the AR-Button I get a black screen and nothing happens. In the end I would like to add marker detection to the existing project.
I tried different version combinations but I dont seem to find a solution (master and dev versions).
If the current behavior is a bug, please provide the steps to reproduce.
<html>

<head>
  <script>
    // WebXR requires https: to work so ensure redirected if needed.
    if (location.hostname !== 'localhost' && window.location.protocol === 'http:') window.location.protocol = 'https:';
  </script>
  <!-- the AFrame library -->
	<script src="https://aframe.io/releases/1.3.0/aframe.min.js"></script>

  <!-- ##### HERE I HAVE ADDED THE SCRIPT TAG  ##### -->
        <script src="https://raw.githack.com/AR-js-org/AR.js/master/aframe/build/aframe-ar.js"></script>

  <!-- include a default environemnt which makes VR  look nice, https://github.com/feiss/aframe-environment-component -->
	<script<EMAIL_ADDRESS>  <!-- this shadow helper ensures that the model has a shadow beneath it -->
  <script src="ar-shadow-helper.js"></script>
  <script src="ar-cursor.js"></script>
	<script src="main.js"></script>

Thank you in advance for your help.

Please mention other relevant information such as the browser version, Operating System and Device Name
I have tried it on my Samsung S10+ in the latest Chrome App
What is the expected behavior?
Expected would be, that the camera starts and one can place the objects somewhere.
If this is a feature request, what is motivation or use case for changing the behavior?

Okay first of all I have forgotten the arjs tag in the a-scene. But besides that ar.js seems to inject the video element right at the beginning no matter what I do. With this code snippet I was able to stop the stream and remove it so when I click on the AR button it seems to work.
    window.addEventListener("arjs-video-loaded", (e) => {
      var videoEl = document.getElementById('arjs-video');
      // now get the stream
      stream = videoEl.srcObject;
      // now get all tracks
      tracks = stream.getTracks();
      // now close each track by having forEach loop
      tracks.forEach(function(track) {
        // stopping every track
        track.stop();
      });
      // assign null to srcObject of video
      videoEl.srcObject = null;
      videoEl.remove();
    });

The problem now is, that marker detection does no work.
Can you help me with that? Thanks in advance.

Nobody who has an idea about this?

Okay first of all I have forgotten the arjs tag in the a-scene. But besides that ar.js seems to inject the video element right at the beginning no matter what I do. With this code snippet I was able to stop the stream and remove it so when I click on the AR button it seems to work.
    window.addEventListener("arjs-video-loaded", (e) => {
      var videoEl = document.getElementById('arjs-video');
      // now get the stream
      stream = videoEl.srcObject;
      // now get all tracks
      tracks = stream.getTracks();
      // now close each track by having forEach loop
      tracks.forEach(function(track) {
        // stopping every track
        track.stop();
      });
      // assign null to srcObject of video
      videoEl.srcObject = null;
      videoEl.remove();
    });

The problem now is, that marker detection does no work.
Can you help me with that? Thanks in advance.

You can't do this, at least i don't reccommend doing this; the arController and other classes are already inited and you can re-init.

The reason that the code doesn't works as you expected could be the aframe version you are using, there are a couple of bugs with newer version than 1.0.4 that are not solved.
Copy and pasting the code is not a good practice. Probably there are some conflictcs with the aframe components from the example and AR.js ( see for example a-scene). You need to identify the source of the problem.

I suggest to you instead to go by little steps adding some code and see in this manner where it fails.


Issue when entering eval window

Hi,
after an update I am having issues when I open and enter eval window by calling lua require("dapui").eval() twice.
The buffer id mentioned in the error is the buffer id of opened eval window.
This does not happen when I only open the window and don't enter it with cursor.
I don't know if this is the issue of nvim-dap-ui or nvim-dap.
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/diagnostic.lua:1426: Invalid buffer id: 8
stack traceback:
        [C]: in function 'nvim_exec_autocmds'
        /usr/share/nvim/runtime/lua/vim/diagnostic.lua:1426: in function 'reset'
        ...config/nvim/plugged/nvim-dap/lua/dap/session.lua:1394: in function 'close'
        ....config/nvim/plugged/nvim-dap/lua/dap/session.lua:698: in function 'callback'
        ...config/nvim/plugged/nvim-dap/lua/dap/session.lua:953: in function <...config/nvim/plugged/nvim-dap/lua/dap/session.lua:945>

I am on latest commit f7fc98ead677ffed72d4eec331eb439a7bad3bbf
neovim version:
:version
NVIM v0.8.0
Build type: Release
LuaJIT 2.1.0-beta3

I think that the issue is caused by recent commit in nvim-dap https://github.com/mfussenegger/nvim-dap/commit/61643680dcb771a29073cd432894e2f81a7c2ae3 for now I reverted back to 0.3.0 on nvim-dap and everything is working as expected.


commFunc -> commFun

Sorry, but this still doesn't really qualify as a good commit message (in my opinion), since it's not even a complete sentence, when looking at the log on e.g. the Git command line.
In this case, something like might be better?
Fix `commFunc` typo in the `SandboxSupportBase.destroy` method

As can be seen in the constructor, the correct name is `commFun` which means it wasn't being cleaned-up properly.


access redux store within asyncValidate

Is it possible to access the redux store within asyncValidate or have some other data passed as parameters into it?

According to the docs, the asyncValidate accepts a props argument.
So you can use connect from react-redux, eg
let MyForm = () => { ... };
MyForm = connect( state => ({
  someValue: state.someValue
}))( MyForm );
MyForm = reduxForm({
  form: "formName",
  asyncValidate ( values, dispatch, props ) {
    console.log( props.someValue );
    return doSomethingAsync();
  }
})( MyForm );

Thank you @gustavohenke! I had no idea I could pass asyncValidate as a prop from the container vs at "design time".


Add better right click handlers for use in test cases

@frqmod fix this to make the nested "Sync from..." work again in the context menus.


Constants typecasted trigger magic number.

const MyConstantValue = float32(20)
This will trigger the check when it is being used as a constant and not as a magic number

@dtracers Thanks for the report!

@dtracers Thanks again for your report. I fixed the bug with version 2.0.2. Feel free to try it out :)


Storage "upload" method do not save metadata on Android

Metadata is not propagated to native code.
https://github.com/fullstackreact/react-native-firestack/blob/master/android/src/main/java/io/fullstack/firestack/FirestackStorage.java#L157
Metadata map is destructured but never used.

@Yarikx will sort on my branch (which is going to be merged for v3)

@Salakar Cool!

Done, on my branch.

Looking forward to merge this -- working on tests

Closing as fixed on v3 branch.


Azure discovery plugin

Please Check also https://github.com/crate/elasticsearch/pull/87

Are there any distribution tests to make sure the things in this PR actually work?

@mfussenegger I created a jenkins job (https://jenkins.crate.io/job/azure-plugin-test/) that is creating 3 node on azure and tests azure discovery plugin. I hope this is what you meant.
In addition when I am using versions.elasticsearch it is compaining that "elastic search version is not specified", that is why I used elasticsearch.version.

lgtm, but maybe let @seut take a look at it as well

thank you @mfussenegger , I will ask him, too

@dobe can you take a look please

changelog

since @dobe is on holidays, @seut you will need to finalise the review of this PR

lgtm


add git lfs prune to maintenance job #3283

Fix #3283.
Thank you for triaging the #3283, @EzzhevNikita.  Can you review and help me get this merged?

I attempted to review the build failures for macOS and Linux ARM and unfortunately receive a 401 error in Microsoft's Azure DevOps environment, likely by design since I'm not an employee.  I've allowed edits by maintainers; I welcome any commits necessary to get past these issues.

@MarkHerhold We will take a look at your PR

Your changes is not the root cause of failed checks, I've restarted them

@EzzhevNikita the x64 pipeline jobs have started failing in the Component Detection stage.  I tried a few things to get past the error but was unsuccessful.  Can you take a look?

Thanks! Let us re-test this also

some comment to trigger ci

/azp run


log X-Real-IP for server behind a https gateway

Thank you for your contribution!
Just a quick confirm before merging: Is the new log format compatible to Apache / Nginx / other HTTP servers?

It's not strict compatible. I'll pull a new fix later.

Thank you for your information.
Waiting for your new pull request.


Abnormal CPU usage in Linux machine

Describe the bug
Abnormal CPU usage in Linux machine
Add: I am unable to reproduce this issue
Add2: Placing it for an additional period of time will trigger the same issue, which seems to be related to UDP/KCP
To Reproduce

Download and start FRPc here, using systemd: https://github.com/fatedier/frp/releases/tag/v0.51.2

the frpc config
[common]
server_addr = my-frps-ip
server_port = 7000
protocol = kcp
token = RqypfsR6hJR2yEWuq
protocol = kcp
pool_count = 1
login_fail_exit = false
heartbeat_interval = 60
heartbeat_timeout = 90
tls_enable = true
tls_trusted_ca_file = /usr/local/share/frp/root.crt
disable_custom_tls_first_byte = false
log_level = info

[vnc_stcp]
type = stcp
role = visitor
server_name = vnc_stcp
sk = 6hJYjbNTgfmzPx3
bind_ip = <IP_ADDRESS>
bind_port = 5900

Expected behavior
Normal CPU usage
Diagnostic report (required)
Diagnostic cannot be used
Screenshots and additional context (optional)
No response

I am uploading screenshots and logs, please wait a moment

log.zip

Fixed for the next version. (That being said, I don't have a stop to reproduce this, so please let me know if not)

Released in v0.15.1.

@sklyar It looks like you have a machine named vpn with a service listening on localhost:9090 that keeps restarting (likely because it crashed). Can you get logs of the crashing service? Also make sure its configuration is correct. It'd be great if you could share what service this is so I can reproduce it.


ISSUE: Try to compile source code in windows

Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting st2-auth-ldap
Cloning https://gitee.com/mirrors_StackStorm/st2-auth-ldap.git (to revision v3.7) to c:\users\lism12\appdata\local\temp\pip-install-7afp9ewd\st2-auth-ldap_2a958b35cc6643e9acf4e601f09f88f2
Resolved https://gitee.com/mirrors_StackStorm/st2-auth-ldap.git to commit a4dc11b040e4a833a5499d579fb83e99c695ac09
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting python-ldap==3.4.0
Using cached https://pypi.tuna.tsinghua.edu.cn/packages/41/e2/6b12190c171b78d1cd8c9d0d3380d18b85959aecb2b1267f7bdd5b66cd8f/python-ldap-3.4.0.tar.gz (376 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting cachetools<2.1.0,>=2.0.1
Using cached https://pypi.tuna.tsinghua.edu.cn/packages/ac/e8/5492fd5ada0b05a1bc485bcb634b559acdec59383eef5c4203b5e22be296/cachetools-2.0.1-py2.py3-none-any.whl (11 kB)
Collecting pyasn1>=0.3.7
Using cached https://pypi.tuna.tsinghua.edu.cn/packages/62/1e/a94a8d635fa3ce4cfc7f506003548d0a2447ae76fd5ca53932970fe3053f/pyasn1-0.4.8-py2.py3-none-any.whl (77 kB)
Collecting pyasn1-modules>=0.1.5
Using cached https://pypi.tuna.tsinghua.edu.cn/packages/95/de/214830a981892a3e286c3794f41ae67a4495df1108c3da8a9f62159b9a9d/pyasn1_modules-0.2.8-py2.py3-none-any.whl (155 kB)
Building wheels for collected packages: st2-auth-ldap, python-ldap
Building wheel for st2-auth-ldap (setup.py): started
Building wheel for st2-auth-ldap (setup.py): finished with status 'done'
Created wheel for st2-auth-ldap: filename=st2_auth_ldap-3.7.0-py3-none-any.whl size=19299 sha256=196380d7794ab72f9413302f0a27e72cd7bc2a35be7959c665efc2f2498ad8c8
Stored in directory: C:\Users\lism12\AppData\Local\Temp\pip-ephem-wheel-cache-t8cf3ke1\wheels\3a\e5\59\bdbf9a2647f759ff4f39f0648b92b5f0168ae4b933038a7e74
Building wheel for python-ldap (pyproject.toml): started
Building wheel for python-ldap (pyproject.toml): finished with status 'error'
Successfully built st2-auth-ldap
Failed to build python-ldap
Running command git clone --filter=blob:none --quiet https://gitee.com/mirrors_StackStorm/st2-auth-ldap.git 'C:\Users\lism12\AppData\Local\Temp\pip-install-7afp9ewd\st2-auth-ldap_2a958b35cc6643e9acf4e601f09f88f2'
Running command git checkout -b v3.7 --track origin/v3.7
branch 'v3.7' set up to track 'origin/v3.7'.
Switched to a new branch 'v3.7'
error: subprocess-exited-with-error
Building wheel for python-ldap (pyproject.toml) did not run successfully.
exit code: 1
[110 lines of output]
C:\Users\lism12\AppData\Local\Temp\pip-build-env-ostbco0v\overlay\Lib\site-packages\setuptools\config\setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
warnings.warn(msg, warning_class)
running bdist_wheel
running build
running build_py
creating build\lib.win-amd64-cpython-38
copying Lib\ldapurl.py -> build\lib.win-amd64-cpython-38
copying Lib\ldif.py -> build\lib.win-amd64-cpython-38
creating build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\async.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\asyncsearch.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\cidict.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\compat.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\constants.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\dn.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\filter.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\functions.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\ldapobject.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\logger.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\modlist.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\pkginfo.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\resiter.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\sasl.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap\syncrepl.py -> build\lib.win-amd64-cpython-38\ldap
copying Lib\ldap_init_.py -> build\lib.win-amd64-cpython-38\ldap
creating build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\deref.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\libldap.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\openldap.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\pagedresults.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\ppolicy.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\psearch.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\pwdpolicy.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\readentry.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\sessiontrack.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\simple.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\sss.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls\vlv.py -> build\lib.win-amd64-cpython-38\ldap\controls
copying Lib\ldap\controls_init_.py -> build\lib.win-amd64-cpython-38\ldap\controls
creating build\lib.win-amd64-cpython-38\ldap\extop
copying Lib\ldap\extop\dds.py -> build\lib.win-amd64-cpython-38\ldap\extop
copying Lib\ldap\extop\passwd.py -> build\lib.win-amd64-cpython-38\ldap\extop
copying Lib\ldap\extop_init_.py -> build\lib.win-amd64-cpython-38\ldap\extop
creating build\lib.win-amd64-cpython-38\ldap\schema
copying Lib\ldap\schema\models.py -> build\lib.win-amd64-cpython-38\ldap\schema
copying Lib\ldap\schema\subentry.py -> build\lib.win-amd64-cpython-38\ldap\schema
copying Lib\ldap\schema\tokenizer.py -> build\lib.win-amd64-cpython-38\ldap\schema
copying Lib\ldap\schema_init_.py -> build\lib.win-amd64-cpython-38\ldap\schema
creating build\lib.win-amd64-cpython-38\slapdtest
copying Lib\slapdtest_slapdtest.py -> build\lib.win-amd64-cpython-38\slapdtest
copying Lib\slapdtest_init_.py -> build\lib.win-amd64-cpython-38\slapdtest
running egg_info
writing Lib\python_ldap.egg-info\PKG-INFO
writing dependency_links to Lib\python_ldap.egg-info\dependency_links.txt
writing requirements to Lib\python_ldap.egg-info\requires.txt
writing top-level names to Lib\python_ldap.egg-info\top_level.txt
reading manifest file 'Lib\python_ldap.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'Doc.build'
adding license file 'LICENCE'
writing manifest file 'Lib\python_ldap.egg-info\SOURCES.txt'
C:\Users\lism12\AppData\Local\Temp\pip-build-env-ostbco0v\overlay\Lib\site-packages\setuptools\command\build_py.py:202: SetuptoolsDeprecationWarning:     Installing 'slapdtest.certs' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'slapdtest.certs' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'slapdtest.certs' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'slapdtest.certs' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

creating build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\README -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\ca.conf -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\ca.pem -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\client.conf -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\client.key -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\client.pem -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\gencerts.sh -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\gennssdb.sh -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\server.conf -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\server.key -> build\lib.win-amd64-cpython-38\slapdtest\certs
copying Lib\slapdtest\certs\server.pem -> build\lib.win-amd64-cpython-38\slapdtest\certs
warning: build_py: byte-compiling is disabled, skipping.
running build_ext
building '_ldap' extension
creating build\temp.win-amd64-cpython-38
creating build\temp.win-amd64-cpython-38\Release
creating build\temp.win-amd64-cpython-38\Release\Modules
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.33.31629\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DHAVE_SASL -DHAVE_TLS -DHAVE_LIBLDAP_R -DHAVE_LIBLDAP_R -DLDAPMODULE_VERSION=3.4.0 "-DLDAPMODULE_AUTHOR=python-ldap project" "-DLDAPMODULE_LICENSE=Python style" -IModules -ID:\app\Anaconda3\envs\st2\include -ID:\app\Anaconda3\envs\st2\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.33.31629\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /TcModules/LDAPObject.c /Fobuild\temp.win-amd64-cpython-38\Release\Modules/LDAPObject.obj
LDAPObject.c
C:\Users\lism12\AppData\Local\Temp\pip-install-7afp9ewd\python-ldap_cda61375a8e44412aeeb1125b331b71e\Modules\common.h(15): fatal error C1083: 无法打开包括文件: “lber.h”: No such file or directory
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.33.31629\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for python-ldap
ERROR: Could not build wheels for python-ldap, which is required to install pyproject.toml-based projects
how to fixed this problem?

StackStorm is developed and tested against the x86_64 architecture on the Linux platform, specifically Ubuntu and CentOS.  The error you're getting is related to your complier environment, for which we can't provide support.
My personal opinion would be to not attempt to get StackStorm running natively on Windows as there is no guarantee that StackStorm will function correctly even if you get past compiler errors and each subsequent upgrade risks breaking which is less than ideal for a production environment.  I'd recommend running StackStorm on a native Linux OS inside a virtual machine or docker container for  Windows hosts.

@nzlosh @armab But I still think there will be a lot of people using windows for learning and development work, so I recommend supporting compilation on windows

StackStorm is open source and supported by volunteers with limited time and resource.  Unless there is an overwhelming demand to run StackStorm natively on Windows, I doubt anyone will be willing to invest in it.
The main demand is to run StackStorm in Kubernetes at cloud providers like Azure/Google/Amazon.  They all run Linux containers.  Windows has WSL and supports both virtual machines and containers.  Mac OS X supports virtual machines and containers.  This means, providing Linux containers (which are publicly available on Docker hub), Linux/Windows and Mac users can run StackStorm on their machines.
That said, if you feel compelled to run StackStorm natively on Windows, you're completely free to do that, but StackStorm maintainers will not be able to provide official support for such an endeavour.