Intermittent failure to build (arm64?!) based cont...
# 🌱|help-and-getting-started
s
Intermittently I get the following failure when running an action such as:
Copy code
yml
---
kind: Build
name: dcd-linux-armv8-rpi-pi4
description: Build the deepcore-daemon for rpi4
type: container
spec:
  dockerfile: "docker/deepcore-daemon/linux-armv8.Dockerfile"
  platforms: [linux/arm64]
  # extraFlags: ["--push"]
  buildArgs:
    CARGO_C_MESON_IMAGE_ID: ${actions.build.cargo-c-meson.outputs.deploymentImageId}
  targetStage: runner-rpi4
  publishId: registry.gitlab.com/aivero/open-source/see/dcd-linux-armv8-rpi-pi4
timeout: 6000
dependencies: [build.cargo-c-meson, run.publish-acms]
# variables:
#   gstreamer-builder-container: ${actions.build.gstreamer-builder.outputs.deploymentImageId}
include:
  - docker/deepcore-daemon/linux-armv8.Dockerfile
...
Copy code
bash
SYNCHRONOUS TERMINATION NOTICE: When explicitly exiting the process via process.exit or via a parent process, asynchronous tasks in your exitHooks will not run. Either remove these tasks, use gracefulExit() instead of process.exit(), or ensure your parent process sends a SIGINT to the process running this code.
node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:87:19)
    at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Node.js v22.9.0
Note that this is on the new cloud container builders.
b
@salmon-scientist-57815 hello, what's the operating system you're using? Are you on Windows? Can you share the complete garden command output with us, and also the command itself?
4 Views