Привет! Принес вам панику при таком сетапе: werf.yaml: ... --- image: scratch from: scratch ... лог: ... ┌ ⛵️ image

scratch
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x301e0bc]
goroutine 231 [running]:
github.com/werf/werf/pkg/build/stage.(*BaseStage).getServiceMountsFromLabels(0xffffffffffffffff?, 0xc002035ea0)
/git/pkg/build/stage/base.go:315 +0x5c
github.com/werf/werf/pkg/build/stage.(*BaseStage).getServiceMounts(0x39dcce0?, 0x4a3a5b8?)
/git/pkg/build/stage/base.go:307 +0x36
github.com/werf/werf/pkg/build/stage.(*FromStage).PrepareImage(0xc001a029c0, {0xc001a029c0?, 0xc0022fd3d8?}, {0x4a2cfd8, 0xc001727600}, {0x4a3a5b8, 0xc000cd5b00}, 0x381ee20?, 0xc0043a2340, {0x0, ...})
/git/pkg/build/stage/from.go:86 +0x194
github.com/werf/werf/pkg/build.(*BuildPhase).prepareStageInstructions(0xc00163d5e0, {0x4a0c068?, 0xc0010df530}, 0xc00074f800?, {0x4a33b00, 0xc001a029c0})
/git/pkg/build/build_phase.go:1035 +0xd4a
github.com/werf/werf/pkg/build.(*BuildPhase).onImageStage(0xc00163d5e0, {0x4a0c068, 0xc0010df530}, 0xc00074f800, {0x4a33b00?, 0xc001a029c0?})
/git/pkg/build/build_phase.go:768 +0x6ff
github.com/werf/werf/pkg/build.(*BuildPhase).OnImageStage.func1(0xc00416c140?, {0x4a33b00, 0xc001a029c0}, 0xc0?)
/git/pkg/build/build_phase.go:700 +0x6c
github.com/werf/werf/pkg/build.(*StagesIterator).OnImageStage(0xc001938480, {0x4a0c068, 0xc0010df530}, 0xc00074f800, {0x4a33b00, 0xc001a029c0}, 0xc0022fda10)
/git/pkg/build/stages_iterator.go:58 +0x2d0
github.com/werf/werf/pkg/build.(*BuildPhase).OnImageStage(0xc00416c130?, {0x4a0c068?, 0xc0010df530?}, 0xc00411d590?, {0x4a33b00?, 0xc001a029c0?})
/git/pkg/build/build_phase.go:696 +0x66
github.com/werf/werf/pkg/build.(*Conveyor).doImage.func2()
/git/pkg/build/conveyor.go:720 +0x9cb
github.com/werf/logboek/internal/stream.(*Stream).logProcess.func1()
/go/pkg/mod/github.com/werf/logboek@v0.5.5/internal/stream/process.go:150 +0x1b
github.com/werf/logboek/internal/stream.(*Stream).logProcess(0xc0013ab050, {0xc0041627c8?, 0x38?}, 0xc00411d3e0, 0xc001938340)
/go/pkg/mod/github.com/werf/logboek@v0.5.5/internal/stream/process.go:157 +0x1cf
github.com/werf/logboek/internal/stream.(*LogProcess).DoError(0xc001938300, 0xc001938340)
/go/pkg/mod/github.com/werf/logboek@v0.5.5/internal/stream/process_types.go:201 +0xa5
github.com/werf/werf/pkg/build.(*Conveyor).doImage(0x0?, {0x4a0c068?, 0xc0010df530}, 0xc00074f800, {0xc001c916a0, 0x1, 0x1})
/git/pkg/build/conveyor.go:702 +0x198
github.com/werf/werf/pkg/build.(*Conveyor).doImagesInParallel.func3({0x4a0c068, 0xc0010df530}, 0xc0018ca778?)
/git/pkg/build/conveyor.go:657 +0x215
github.com/werf/werf/pkg/util/parallel.DoTasks.func1()
/git/pkg/util/parallel/parallel.go:83 +0x304
created by github.com/werf/werf/pkg/util/parallel.DoTasks
/git/pkg/util/parallel/parallel.go:76 +0x25c

Я понимаю, что так не надо делать, но раз случайно получилось - значит есть варианты)))
версия: v1.2.263, контейнерная

С buildah скорее всего эту историю мы можем обойти, но вообще при использовании stapel есть известное ограничение по sctatch — https://github.com/werf/werf/issues/2841.