Balena CLI in Docker Container

Product support
1

I am using Codeship Pro as my CI/CD pipeline which builds my Dockerfile from alpine:3.8 and installs Balena CLI via npm. A docker-compose.yml (containing 3 services) is copied into the image and a deploy.sh file is copied into the image (where Balena CLI commands are executed).

When the container is run and deploy.sh is invoked, the CLI output logs list [Build] Built 3 services in 0 seconds followed by [Error] Build failed. No such file or directory: /dev/fd/12

Could anyone point me in the right direction to debug this scenario?

4

@scubacyclecode could you provide a link to the compse & deploy script?

6

Dockerfile used to execute the Balena CLI, https://gist.github.com/doniosjm/568de494ff455f54b8e8394eac22f0f9

docker-compose.yml for Balena services (reduced it to 1 service for the purposes of testing), https://gist.github.com/doniosjm/debd8de23dae9bf57b228c575fe413d3

deploy.sh, https://gist.github.com/doniosjm/0a01d4c9a0306b644affefbefd392d25

7

I found 2 issues here and I will consider the issue resolved.

  1. I was building the Dockerfile from the root (oops).
  2. Codeship does allow containers to be run in privileged mode, which Balena CLI requires.
1 Like
8

@scubacyclecode I am glad you resolved it, but thanks for sending through the files anyway.