mirror of
https://github.com/docker/compose.git
synced 2026-11-20 15:09:50 +00:00
A service declaring only build: (no image:) answered get-service-config with an empty "image" field: service.Image is the YAML-declared value, and compose-go never fills it in for this case (every other caller of GetImageNameOrDefault in this package exists precisely because of that). The provider only ever sees this response, never the model compose builds internally, so an sbx-style provider building its own runtime image rejected the service outright with "defines no image". The response now carries the resolved name (api.GetImageNameOrDefault) instead - the same one the image phase already built and tagged by the time a provider asks. The build directive itself is cleared before marshaling: a provider has no builder to run it against, only an image identity to run. Pinned by a regression test using the existing fake-provider harness, verified by ablation to fail on either half of the fix reverted. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| api | ||
| bridge | ||
| compose | ||
| dryrun | ||
| e2e | ||
| mocks | ||
| remote | ||
| utils | ||
| watch | ||