Hi,
I have noticed in the last couple of days that pushing images to the Balena image registry is taking a very long time. I have 8 services in my Balena release, one is large (~9.5GB). Before Feb 1st, pushing the images to the registry was taking ~10 minutes. After Feb 1 it is taking ~1.5 hours. I am just wondering if something has changed recently?
I am running the balena deploy command from the balena-cli to build and push images. Most images are built and pushed to AWS ECR first, not build as a part of the balena deploy command.
my docker compose file looks like this:
version: "2"
services:
service_1:
image: aws-ecr.com/engine:service_1-v1
network_mode: host
volumes:
- shared-data:/shared
- service_1_data:/data
privileged: true
labels:
io.balena.features.dbus: "1"
io.balena.features.supervisor-api: "1"
io.balena.features.balena-api: "1"
service_2:
build:
context: service_2
args:
- BASE=aws-ecr.com/engine:service_2-prod-v1
volumes:
- service_2-data:/data
network_mode: host
privileged: true
service_3:
image: aws-ecr.com/engine:service_3-v1
network_mode: host
privileged: true
labels:
io.balena.features.dbus: "1"
service_4:
image: aws-ecr.com/engine:service_4-v1
network_mode: host
restart: "no"
service_5:
image: aws-ecr.com/engine:service_5-v1
network_mode: host
service_6:
image: aws-ecr.com/engine:service_6-v1
network_mode: host
privileged: true
labels:
io.balena.features.supervisor-api: "1"
io.balena.features.dbus: "1"
service_7:
image: aws-ecr.com/engine:service_7-v1
network_mode: host
privileged: true
restart: "no"
pid: "host"
labels:
io.balena.features.dbus: "1"
io.balena.features.supervisor-api: "1"
service_8:
image: aws-ecr.com/engine:service_8-v1
privileged: true
pid: host
network_mode: host
volumes:
- service_8-data:/data
tmpfs:
- /tmp-logs
labels:
io.balena.features.dbus: "1"
io.balena.features.supervisor-api: "1"
io.balena.features.balena-socket: "1"
io.balena.features.journal-logs: "1"
volumes:
shared-data:
service_1_data:
service_2-data:
service_8-data:
Thanks for any help.