【发布时间】:2023-01-11 06:13:15
【问题描述】:
我刚刚更新了适用于 Windows 的 docker 桌面,当我运行 docker compose up --build app 以在文件更改后刷新远程图像时,出现以下错误。其他所有撰写命令似乎都是有序的。
Docker 撰写版本:v2.12.2
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x187d8c6]
goroutine 12 [running]:
github.com/docker/compose/v2/pkg/compose.(*composeService).getDrivers(0xc000399f80, {0x20a2448, 0xc0005d8db0})
github.com/docker/compose/v2/pkg/compose/build_buildkit.go:95 +0xc6
github.com/docker/compose/v2/pkg/compose.(*composeService).doBuildBuildkit(0xc000399f80, {0x20a2448, 0xc0005d8db0}, 0x0?, {0x1d918cd, 0x4})
github.com/docker/compose/v2/pkg/compose/build_buildkit.go:47 +0x87
github.com/docker/compose/v2/pkg/compose.(*composeService).doBuild(0xc000399f80, {0x20a2448, 0xc0005d8db0}, 0xc0005a55e0?, 0xc0004b1ad0, {0x1d918cd, 0x4})
github.com/docker/compose/v2/pkg/compose/build.go:228 +0xc5
github.com/docker/compose/v2/pkg/compose.(*composeService).ensureImagesExists(0x0?, {0x20a2448, 0xc0005d8db0}, 0xc0005a55e0, 0x0)
github.com/docker/compose/v2/pkg/compose/build.go:134 +0x14d
github.com/docker/compose/v2/pkg/compose.(*composeService).create(0xc000399f80?, {0x20a2448, 0xc0005d8db0}, 0xc0005a55e0, {{0xc000178a80, 0x1, 0x2}, 0x0, 0x0, {0x1d97342, ...}, ...})
github.com/docker/compose/v2/pkg/compose/create.go:67 +0x173
github.com/docker/compose/v2/pkg/compose.(*composeService).Up.func1({0x20a2448, 0xc0005d8db0})
github.com/docker/compose/v2/pkg/compose/up.go:36 +0xaa
github.com/docker/compose/v2/pkg/progress.Run.func1({0x20a2448?, 0xc0005d8db0?})
github.com/docker/compose/v2/pkg/progress/writer.go:61 +0x27
github.com/docker/compose/v2/pkg/progress.RunWithStatus.func2()
github.com/docker/compose/v2/pkg/progress/writer.go:82 +0x87
golang.org/x/sync/errgroup.(*Group).Go.func1()
golang.org/x/sync@v0.0.0-20220819030929-7fc1605a5dde/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
golang.org/x/sync@v0.0.0-20220819030929-7fc1605a5dde/errgroup/errgroup.go:72 +0xa5
【问题讨论】:
-
这听起来更像是一个 Docker 错误,而不是 SO 社区可以帮助解决的问题。但以防万一,回溯本身并不足以提供帮助;你可以edit 问题包括minimal reproducible example 吗?
标签: node.js docker docker-compose