CLI balena preload hangs at "Reading image information"

fritz · November 15, 2022, 11:17am

Hi,
I’ve searched across various similar topics but could not find a solution.
I’m trying to preload an app to an image for flashing, but the process is stuck at “Reading image information”.
Command:

DEBUG=1 balena preload ~/Downloads/balena-cloud-manufacturing-raspberrypi0-2w-64-2.87.16+rev1-v12.11.0.img --fleet manufacturing --commit latest

Output:

[debug] original argv0="/usr/local/lib/balena-cli/bin/node" argv=[/usr/local/lib/balena-cli/bin/node,/usr/local/lib/balena-cli/bin/run,preload,/Users/fritz/Downloads/balena-cloud-manufacturing-raspberrypi0-2w-64-2.87.16+rev1-v12.11.0.img,--fleet,manufacturing,--commit,latest] length=8
[debug] new argv=[/usr/local/lib/balena-cli/bin/node,/usr/local/lib/balena-cli/bin/run,preload,/Users/fritz/Downloads/balena-cloud-manufacturing-raspberrypi0-2w-64-2.87.16+rev1-v12.11.0.img,--fleet,manufacturing,--commit,latest] length=8
[debug] Deprecation check: 0.05941 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[debug] Event tracking error: Timeout awaiting 'response' for 0ms
Building Docker preloader image. [===                     ] 12%
Step 1/7 : FROM alpine:3.12
Building Docker preloader image. [======                  ] 25%
Step 2/7 : WORKDIR /usr/src/app
 ---> Using cache
Building Docker preloader image. [=========               ] 37%
Step 3/7 : RUN apk add --no-cache curl py3-pip parted btrfs-progs util-linux sfdisk file coreutils sgdisk e2fsprogs-extra docker
 ---> Using cache
Building Docker preloader image. [============            ] 50%
Step 4/7 : COPY requirements.txt ./
 ---> Using cache
Building Docker preloader image. [===============         ] 62%
Step 5/7 : RUN pip3 install --no-cache-dir -r requirements.txt
 ---> Using cache
Building Docker preloader image. [==================      ] 75%
Step 6/7 : COPY src/ ./
 ---> Using cache
Building Docker preloader image. [=====================   ] 87%
Step 7/7 : CMD ["python3", "/usr/src/app/preload.py"]
 ---> Using cache
 ---> 0cafc2659267
Successfully built 0cafc2659267
Building Docker preloader image. [========================] 100%
| Checking that the image is a writable file
| Finding a free tcp port
| Checking if the image is an edison zip archive
- Creating preloader container
/ Starting preloader container
- Fetching application matthias1/manufacturing
- Reading image information

Any ideas?
Thanks

fritz · November 15, 2022, 11:20am

I just tried to do
balena logout
and then balena login.
Now I’m getting the following error:

[debug] original argv0="/usr/local/lib/balena-cli/bin/node" argv=[/usr/local/lib/balena-cli/bin/node,/usr/local/lib/balena-cli/bin/run,preload,/Users/fritz/Downloads/balena-cloud-manufacturing-raspberrypi0-2w-64-2.87.16+rev1-v12.11.0.img,--fleet,manufacturing,--commit,latest] length=8
[debug] new argv=[/usr/local/lib/balena-cli/bin/node,/usr/local/lib/balena-cli/bin/run,preload,/Users/fritz/Downloads/balena-cloud-manufacturing-raspberrypi0-2w-64-2.87.16+rev1-v12.11.0.img,--fleet,manufacturing,--commit,latest] length=8
[debug] Deprecation check: 0.06406 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[debug] Event tracking error: Timeout awaiting 'response' for 0ms
Building Docker preloader image. [===                     ] 12%
Step 1/7 : FROM alpine:3.12
Building Docker preloader image. [======                  ] 25%
Step 2/7 : WORKDIR /usr/src/app
 ---> Using cache
Building Docker preloader image. [=========               ] 37%
Step 3/7 : RUN apk add --no-cache curl py3-pip parted btrfs-progs util-linux sfdisk file coreutils sgdisk e2fsprogs-extra docker
 ---> Using cache
Building Docker preloader image. [============            ] 50%
Step 4/7 : COPY requirements.txt ./
 ---> Using cache
Building Docker preloader image. [===============         ] 62%
Step 5/7 : RUN pip3 install --no-cache-dir -r requirements.txt
 ---> Using cache
Building Docker preloader image. [==================      ] 75%
Step 6/7 : COPY src/ ./
 ---> Using cache
Building Docker preloader image. [=====================   ] 87%
Step 7/7 : CMD ["python3", "/usr/src/app/preload.py"]
 ---> Using cache
 ---> 0cafc2659267
Successfully built 0cafc2659267
Building Docker preloader image. [========================] 100%
| Checking that the image is a writable file
| Finding a free tcp port
| Checking if the image is an edison zip archive
| Creating preloader container
| Cleaning up temporary files
(HTTP code 409) unexpected - Conflict. The container name "/balena-image-preloader" is already in use by container "2638bf8a8cf93f05a51607415cb19455aff0c02749e4eae45b83b81047f015ef". You have to remove (or rename) that container to be able to reuse that name. 

Error: (HTTP code 409) unexpected - Conflict. The container name "/balena-image-preloader" is already in use by container "2638bf8a8cf93f05a51607415cb19455aff0c02749e4eae45b83b81047f015ef". You have to remove (or rename) that container to be able to reuse that name. 
    at /usr/local/lib/balena-cli/node_modules/docker-modem/lib/modem.js:315:17
    at getCause (/usr/local/lib/balena-cli/node_modules/docker-modem/lib/modem.js:345:7)
    at Modem.buildPayload (/usr/local/lib/balena-cli/node_modules/docker-modem/lib/modem.js:314:5)
    at IncomingMessage.<anonymous> (/usr/local/lib/balena-cli/node_modules/docker-modem/lib/modem.js:286:14)
    at IncomingMessage.emit (events.js:326:22)
    at IncomingMessage.EventEmitter.emit (domain.js:483:12)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
From previous event:
    at processImmediate (internal/timers.js:461:21)
From previous event:
    at Preloader.prepare (/usr/local/lib/balena-cli/node_modules/balena-preload/build/preload.js:660:48)
    at PreloadCmd.prepareAndPreload (/usr/local/lib/balena-cli/build/commands/preload.js:292:25)
    at /usr/local/lib/balena-cli/build/commands/preload.js:129:30
    at new Promise (<anonymous>)
    at PreloadCmd.run (/usr/local/lib/balena-cli/build/commands/preload.js:127:19)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async PreloadCmd._run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async Config.runCommand (/usr/local/lib/balena-cli/node_modules/@oclif/config/lib/config.js:175:24)
    at async CustomMain.run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/main.js:27:9)
    at async CustomMain._run (/usr/local/lib/balena-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async /usr/local/lib/balena-cli/build/app.js:76:13
    at async Promise.all (index 2)
    at async oclifRun (/usr/local/lib/balena-cli/build/app.js:94:5)
    at async Object.run (/usr/local/lib/balena-cli/build/app.js:107:9)
    at async run (/usr/local/lib/balena-cli/bin/run:20:2)

For further help or support, visit:
https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting

How can I remove (or rename) this container?
Thanks

fritz · November 15, 2022, 1:30pm

So, I could delete the container, now I’m stuck (again) at the previous issue, hanging at “Reading image information”.

aethernet · November 16, 2022, 8:53am

Hello,

I’ll continue here as it might be useful for the community.

As the CLI preloader is using your local docker demon to run the preloading process, it starts a balena-image-preloder container. When it crashed on your first time, that container hasn’t been properly disposed of, so your second attempt fails.

To remove it you can use the docker cli : docker stop balena-image-preloder && docker rm balena-image-preloder.

For your other issue, can you try using the fleet id instead of name ?

aethernet · November 16, 2022, 9:18am

I double check and using fleet name should work fine.

Which makes your logout/login a good idea, if it wasn’t stuck by the previous attempt.

Which version of docker and cli are you using ?

fritz · November 16, 2022, 4:11pm

Hi @aethernet
thanks for your reply. I’m using Docker version 20.10.17, build 100c701
and Balena CLI 14.5.10
(I upgraded yesterday because it did not work before with 14.4, which I had installed previously).

I’ve been using this command exactly that way for years now, so there must be some new issue somewhere, which I don’t see.
Any ideas?
Thanks

aethernet · November 16, 2022, 4:45pm

Hello,

I’ve just reproduced on my end and will investigate.
In the meantime you can downgrade the CLI (I’ve preloaded with v13.6.0 earlier today successfully).

aethernet · November 16, 2022, 4:54pm

FYI I just opened a GitHub issue

aethernet · November 16, 2022, 5:05pm

Sorry, the issue is not with the CLI but with a regression in docker 20.10.17, you can downgrade docker as a workaround. (CLI preloading code didn’t change between 13.6 and 14.5 anyway).

fritz · November 16, 2022, 6:34pm

Hi,
thanks, I can confirm downgrading to Docker Desktop 4.9.1 with Docker Engine 20.10.16 resolved the issue.
Cheers

aethernet · November 16, 2022, 7:58pm

Awesome !

We’re working on a fix, should be quick.

tomrankin · December 7, 2022, 4:03pm

Just chiming in, waiting for a fix here.

Regards

aethernet · December 12, 2022, 1:43pm

Hello,

This should be fixed by v14.5.15

rohitsharmar2p · March 20, 2023, 10:57am

Hi I am facing this problem on

❯ docker --version
Docker version 23.0.1, build a5ee5b1dfc

❯ balena --version
15.1.1

Command run

balena preload <IMAGENAME> --fleet <MYFLEET> --commit <COMMIT ID> -p --splash-image <MYSPLASH>

Output

Building Docker preloader image. [========================] 100%
| Checking that the image is a writable file
| Finding a free tcp port
- Creating preloader container
/ Starting preloader container
\ Fetching application <MYFLEET>
\ Reading image information

I think this problem is reappeared on docker version 23.

Anyone else faced this issue on latest docker ?

fish · March 23, 2023, 10:33am

@aethernet can please check this issue found by @rohitsharmar2p

rohitsharmar2p · April 14, 2023, 7:28am

Hi Marc (@mpous) do you know if there is any upcoming fix for balena-cli for docker version 23 which is showing this issue?

mpous · April 14, 2023, 10:02am

@rohitsharmar2p could you please confirm what OS and machine you were using?

I will try to replicate myself!

Thanks for the ping

rohitsharmar2p · April 14, 2023, 11:23am

Hi @mpous its raspberry pi cm4 and I am running os version 2.112.12
I tried also on intel nuc with os version 2.108.19-prod with same issue

mpous · April 14, 2023, 11:32am

@rohitsharmar2p no, i meant what device are you using to run balena preload?

rohitsharmar2p · April 14, 2023, 11:45am

@mpous
I am using Arch linux
my kernel version is 6.2.10-arch1-1

Topic		Replies	Views
Preloading stuck on "Reading Image Information" Product support	0	113	December 13, 2023
Unable to preload and image now? Product support raspberrypi3	23	3072	January 20, 2020
balena preload not working iot-gate-imx8plus Product support	1	143	November 29, 2023
balena push hanging on uploading Product support balena-cli	3	420	August 15, 2023
Unable to create preload image Product support balena-cli	1	25	August 2, 2024

CLI balena preload hangs at "Reading image information"

Related topics