moby/builder/builder-next
Tonis Tiigi d250e13945
builder-next: fix missing lock in ensurelayer
When this was called concurrently from the moby image
exporter there could be a data race where a layer was
written to the refs map when it was already there.

In that case the reference count got mixed up and on
release only one of these layers was actually released.

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
(cherry picked from commit 37545cc644)
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
2024-03-07 12:18:07 +01:00
..
adapters builder-next: fix missing lock in ensurelayer 2024-03-07 12:18:07 +01:00
exporter migrate to github.com/containerd/log v0.1.0 2023-10-11 17:52:23 +02:00
imagerefchecker remove unneeded "digest" alias for "go-digest" 2022-03-04 14:49:42 +01:00
worker builder-next: fix timing filter for default policy 2023-11-28 22:37:30 -08:00
builder.go vendor: github.com/moby/buildkit v0.12.3-dev 2023-10-13 17:05:56 -07:00
controller.go vendor: github.com/moby/buildkit v0.12.5 2024-01-31 21:24:39 +01:00
executor_linux.go daemon/config: change DNSConfig.DNS to a []net.IP 2023-11-13 12:22:51 +01:00
executor_nolinux.go vendor: github.com/moby/buildkit v0.12.2 2023-09-21 14:18:45 -06:00
reqbodyhandler.go builder-next: use constants for http status codes 2019-10-13 19:11:24 +02:00