This might be more appropriate under balena cli, but I didn’t see that as a standalone category.
I have the following
docker-compose.yml that I am deploying with like the following:
balena deploy myApp.
docker-compose.yml is as follows:
version: '2' services: service1: image: <google-container-registry-image> service2: build: context: /Users/me/dev/some/path/rootOfService2
service1 is a Java application that is built with jib. I’m building that container in a separate step and then just pulling from my container registry. service2 is a simpler python container. I’d like to be able to specify an absolute path (ideally, with a env variable) for the build context and build the container using
balena deploy. The path that I’m specifying containers a Dockerfile for service2.
This is the error the CLI gives me:
$ balena deploy myApp [Info] Compose file detected [Info] Building for aarch64/raspberrypi4-64 [Info] Docker Desktop detected (daemon architecture: "x86_64") [Info] Docker itself will determine and enable architecture emulation if required, [Info] without balena-cli intervention and regardless of the --emulated option. [Build] Built 1 service in 0 seconds [Build] <service2> Preparing... [Error] Deploy failed Could not find a Dockerfile for this service Additional information may be available by setting a DEBUG=1 environment variable: "set DEBUG=1" on a Windows command prompt, or "export DEBUG=1" on Linux or macOS. If you need help, don't hesitate in contacting our support forums at https://forums.balena.io For bug reports or feature requests, have a look at the GitHub issues or create a new one at: https://github.com/balena-io/balena-cli/issues/
Any ideas? Is this combination of using a prebuilt image and building another image supported? Am I deviating too far from the recommended balena workflow/project hierarchy?
Thanks for taking a look.