We are in the process of creating a release. However when pushing the release for testing to a device in local mode with 'balena push ’ one of the services is rebuild everytime even though nothing changes. It takes about 1 hour to build the entire docker so our development is seriously compromised at the moment. What could possibly cause this?
We do not use an option like =’–no-cache’ nor do we change anything in the dockerfile or docker-compose.yaml file. We are running host OS version: balenaOS 2.58.6+rev1 and supervisor version
[UPDATE] 12-03-2021 14:56
I’ve upgraded to balena-cli version 12.40.4 and I was still experiencing the same issues.
Next I simplified the docker. It now only contains the following:
FROM debian:buster ENV DEBIAN_FRONTEND=noninteractive # Install git and ssh RUN apt update && apt install -y --no-install-recommends \ openssh-client \ git && \ apt clean && rm -rf /var/lib/apt/lists/* RUN apt update CMD ["/bin/bash"]
This loads the cache but gives the following error:
[Error] There was an error rebuilding the service: InvalidArgumentError: Dockerfile with 2 stages provided, but 0 image IDs passed to livepush constructor (there should be 1)
It is important to note that the dockerfile in question was a multi-stage docker. Also when compiling with docker I don’t experience any issues.