Docker commit running for many hours and still not completed

Docker Desktop
1

Hi, here is the command I invoked from powershell:

docker container commit e07768c308ff ghcr.io/gsequencer/ags-ms-servercore

This command was launched about 4 hours ago.

Why does it take so long?

The df command showed me that it was using 30 % of the filesystem of total 20 GB.

Further, this is the 4th attempt to commit.

#1 After 2 days of commiting, I hit Ctrl-C in command line caused to mess all docker images. They are lost, now.

#2,3 After one day of commiting, the next morning the computer looked like performed a restart. Commit wasn’t successful and was gone.

#4 Is running more than 4 hours not completed yet.

I am using a recent notebook with AMD Ryzen 5 CPU and NVME.

Docker version 20.10.7, build f0df350

My Windows 10 version is:

20H2 Build 19042.1083

Update, it is still doing commit, the fan of the notebook spins and never went sleep, I have disabled hibernation. Further the resource monitor shows CPU activity.

Screenshot 2021-07-08 113810
Screenshot 2021-07-08 1138101920×1080 95.3 KB

by Joël

2

Here is a extraction of some related log file

[06:16:59.688][SegmentApi        ][Info   ] Usage statistic: heartbeat
[06:17:00.421][ApiProxy          ][Info   ] msg="proxy >> HEAD /_ping\n"
[06:17:00.421][ApiProxy          ][Info   ] msg="proxy << HEAD /_ping (537.7µs)\n"
[06:17:00.436][ApiProxy          ][Info   ] msg="proxy >> POST /v1.41/commit?author=&comment=&container=e07768c308ff&repo=ghcr.io%2Fgsequencer%2Fags-ms-servercore&tag=latest\n"
[06:17:13.745][ApiProxy          ][Info   ] msg="Cancel connection..."
[06:17:13.745][ApiProxy          ][Info   ] msg="proxy >> GET /v1.41/events\n"
[06:17:13.745][ApiProxy          ][Info   ] msg="proxy << GET /v1.41/events (5m0.0099508s)\n"
[06:17:40.992][ApiProxy          ][Info   ] msg="proxy >> HEAD /_ping\n"
[06:17:40.992][ApiProxy          ][Info   ] msg="proxy << HEAD /_ping (892.7µs)\n"
[06:17:41.005][ApiProxy          ][Info   ] msg="proxy >> GET /v1.41/images/json\n"
[06:17:41.008][ApiProxy          ][Info   ] msg="proxy << GET /v1.41/images/json (2.6505ms)\n"
[06:17:41.039][GoBackendProcess  ][Info   ] msg="(fff2bb01) c29ed673-CliAPI S<-C Go-http-client/1.1 POST /usage[[STACK]]"
[06:17:41.039][GoBackendProcess  ][Info   ] msg="(fff2bb01) c29ed673-CliAPI S<-C Go-http-client/1.1 bind: {\"command\":\"images\",\"context\":\"moby\",\"status\":\"success\",\"source\":\"cli\"}"
[06:17:41.039][GoBackendProcess  ][Info   ] msg="received new cli usage: {Command:images Context:moby Status:success Source:cli}"
[06:17:41.039][GoBackendProcess  ][Info   ] msg="(fff2bb01-1) 11982578-BackendCMD C->S POST /usage/cli: {\"command\":\"images\",\"context\":\"moby\",\"status\":\"success\",\"source\":\"cli\"}"
[06:17:41.053][IPCServer         ][Info   ] (fff2bb01-1) d2a82050-CSharpAPI S<-C 11982578-BackendCMD POST /usage/cli
github.com/docker/pinata/common/pkg/gui.(*guiClient).CliUsage(0xc00001c3f0, 0xc000048580, 0xc000448380, 0x27ed788)
	C:/workspaces/master-merge/src/github.com/docker/pinata/common/pkg/gui/client.go:211 +0x82
github.com/docker/pinata/common/cmd/com.docker.backend/internal/server.appendCliRoutes.func2(0x27ef0d8, 0xc000448380, 0x4, 0x256b62e)
	C:/workspaces/master-merge/src/github.com/docker/pinata/common/cmd/com.docker.backend/internal/server/routes.go:133 +0x282
[06:17:41.064][IPCServer         ][Info   ] (fff2bb01-1) d2a82050-CSharpAPI S->C 11982578-BackendCMD POST /usage/cli (3ms): OK
[06:17:41.067][GoBackendProcess  ][Info   ] msg="(fff2bb01-1) 11982578-BackendCMD C<-S d2a82050-CSharpAPI POST /usage/cli (27.7973ms): OK"
[06:17:41.067][GoBackendProcess  ][Info   ] msg="(fff2bb01) c29ed673-CliAPI S->C Go-http-client/1.1 POST /usage (27.7973ms): OK"
[06:22:13.747][ApiProxy          ][Info   ] msg="Cancel connection..."
[06:22:13.747][ApiProxy          ][Info   ] msg="proxy >> GET /v1.41/events\n"
[06:22:13.748][ApiProxy          ][Info   ] msg="proxy << GET /v1.41/events (5m0.0017891s)\n"
[06:27:13.748][ApiProxy          ][Info   ] msg="Cancel connection..."
[06:27:13.749][ApiProxy          ][Info   ] msg="proxy >> GET /v1.41/events\n"
[06:27:13.749][ApiProxy          ][Info   ] msg="proxy << GET /v1.41/events (5m0.000466s)\n"
[06:32:13.749][ApiProxy          ][Info   ] msg="Cancel connection..."
[06:32:13.749][ApiProxy          ][Info   ] msg="proxy >> GET /v1.41/events\n"
[06:32:13.749][ApiProxy          ][Info   ] msg="proxy << GET /v1.41/events (5m0.0008683s)\n"
[06:37:13.762][ApiProxy          ][Info   ] msg="Cancel connection..."

There are more “Cancel Connection…” messages in the logs but not many.