Problems getting started with Blocks

Product support
1

I’m having problems getting started with the BalenaHub blocks feature.

I’m trying to develop a variant of the balena-io-experimental/browser-aarch64 block to merge in a couple of features v2.10.0 of that block does not have (primarily rpi-zero2w support, also modernizing to move off deprecated balenalib base images).

The initial block I created in the BalenaHub web was called tl-browser. When I had a first cut of the code ready to push, I entered the command
“balena push gh_tim_littlefair/tl-browser” but this failed with a Javascript stack trace which I did not preserve at the time).

I did manage to push an initial release to this block using a the alternate git-based workflow (command “git push balena 250715-tl_balena_browser_block:master” as I was pushing from a local branch), and this gave me a release I could work with on BalenaHub. I then tried (unsuccessfully) to drop the new block in as a replacement for bh.cr/balenalabs/browser-aarch64 in my target application and deploy this to a device in local mode. While trying to make the local mode deploy work I made the block public as I was getting an error message like this:

[Info]    Starting build on device 192.168.1.181
Some services failed to build:
       balenalabs-browser: (HTTP code 404) unexpected - pull access denied for bh.cr/gh_tim_littlefair/tl-browser, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

After I had this problem I stupidly renamed the original tl-browser repository to tl-browser-aarch64, found that that broke the git workflow for me (both with the old and new version of the block name), deleted and recreated the renamed block. After all this messing about I wasn’t suprised I couldn’t get anything working with my original preferred renamed name, so I started from a fresh block.

The errors I now get on a block called ‘fb99’ (a short name I’ll delete and throw away once I know what works) are as follows with the balena CLI workflow:

$ balena push --debug gh_tim_littlefair/fb99
[debug] new argv=[/home/tim/Applications/balena/bin/node,/home/tim/Applications/balena/bin/run,push,gh_tim_littlefair/fb99] length=4
[debug] Deprecation check: 5.95192 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]   Using build source directory: . 
[Debug]   Pushing to cloud for fleet: gh_tim_littlefair/fb99
[debug] Event tracking error: Timeout awaiting 'response' for 0ms
| Packaging the project source...[Debug]   Tarring all non-ignored files...
/ Packaging the project source...[Debug]   docker-compose.yml file found at "/home/tim/github/tl-balena-browser"
- Packaging the project source...[Debug]   Tarring complete in 240 ms
[debug] Connecting to builder at https://builder.balena-cloud.com/v3/build?slug=gh_tim_littlefair%2Ffb99&dockerfilePath=&emulated=false&nocache=false&headless=false&isdraft=false
Oops something went wrong, please check your connection and try again.

RequestError
    at ClientRequest.<anonymous> (/home/tim/Applications/balena/node_modules/got/dist/source/core/index.js:970:111)
    at Object.onceWrapper (node:events:633:26)
    at ClientRequest.emit (node:events:530:35)
    at origin.emit (/home/tim/Applications/balena/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
    at emitErrorEvent (node:_http_client:104:11)
    at TLSSocket.socketErrorListener (node:_http_client:518:5)
    at TLSSocket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1139:18)
    at internalConnectMultiple (node:net:1215:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
    at listOnTimeout (node:internal/timers:590:11)
    at process.processTimers (node:internal/timers:523:7)

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

(edited a couple of hours after creation to remove complaints about git workflow not working as I worked out what my mistake was and this is OK now).

2

I’ve now managed to get most of it working, but the ‘balena push’ workflow still doesn’t work for me where the target is a block not a fleet. Not urgent anyway as the git workflow is fine for what I am trying to achieve at the moment.

3

Hi, can you please share the exact command you are using for balena push to a block and the output from the command? Please also let us know the version of the CLI you are running; you can find the CLI version by running balena version

4

I’ve repeated the step today, and pushing using the ‘balena push’ workflow is now working correctly for my block, so no furrther action.

The version of balena CLI I was using (both today and on 15 July is 22.1.1, downloaded about 3 weeks ago when I started working on the Balena aspect of this project.

So thanks for checking in, but it looks like there’s nothing can be done now.

1 Like