compose build dependencies

version: '2.4'

services:
  service-core:
    image: custom/service-core
    build:
      context: .
      dockerfile: service-core.dockerfile

  service-base:
    image: custom/service-base
    build:
      context: .
      dockerfile: service-base.dockerfile
    depends_on:
      - service-core

service-base.dockerfile

FROM custom/service-core:latest

running balena push 4fb4e72.local

results in the following error:
service-base: pull access denied for custom/service-core, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied

how do I specify to use a built image as the starting point for another image? Does balena compose have a dependency resolver?

Hello @pateco,

I’m facing the same issue and I’m very interested to know if you found an answer.

Regards,
Gabriel

Hey there, just to clarify your use case, is custom/service-core a locally built image, or is it in a registry somewhere?

I see that you are using balena push which means it’s running on our cloud builders, and by default it will pull the previous release of the image for caching to save build time. Is that what you were hoping to accomplish?