Support transferring pre-built images when balena push is used in local mode

[roman-mazur]

When users utilize docker buildx functionality to build multi-arch images that can work both on their dev machine and on the target device, they cannot easily refer to such pre-built images from docker-compose file.

Currently, pre-built images must be published to some registry. And users don't have direct access to balena's registry.

The feature request is to transfer such pre-built images (using the correct arch variant) from the dev machine to the target device in local mode whenbalena push is executed.

[balena-ci]

[roman-mazur] This issue has attached support thread https://jel.ly.fish/#/support-thread~411105ad-53e0-49d1-bc35-16a92589519e

[pdcastro]

In case this hint is helpful to anyone, I sometimes transfer images between my laptop and a balena device with the commands:

# from laptop to device
docker save my_image | ssh my_device balena-engine load

# from device to laptop
ssh my_device balena-engine save my_image | docker load

where "my_device" is an entry in the ~/.ssh/config file such as:

Host my_device
    User root
    Port 22222
    Hostname 192.168.0.21
    IdentityFile ~/.ssh/id_rsa

I haven't yet used multi-arch images and I wonder how the commands above could be adapted in order to "select the correct arch variant".

[pdcastro]

Connects to:

• balena push selects incorrect image (multiarch images, Docker manifest) #1408 (balena push selects incorrect image (multiarch images, Docker manifest))
• balena build / deploy --build selects base image of wrong architecture (multiarch image manifest) #1508 (Balena build unable to interpret dockerfile image manifests)

[balena-ci]

[shaunmulligan] This issue has attached support thread https://jel.ly.fish/#/ded1c61d-3cd4-4600-9d86-71da0880b440

[balena-ci]

[thgreasi] This issue has attached support thread https://jel.ly.fish/#/bd9c64b2-d60f-4596-a045-16db2d96350d

[jellyfish-bot]

[tmigone] This issue has attached support thread https://jel.ly.fish/#/76e99687-0a3e-4e59-9ef5-bd157fdfbf38

[jellyfish-bot]

[cmfcruz] This issue has attached support thread https://jel.ly.fish/#/132cab21-904d-4535-adae-a4a3dbb8c296

[srd424]

It would be great if balena deploy could take a <uuid>.local hostname instead of a fleet name, like balena push does.