No docker services start when running on Raspberry pi 3

Product support
1

Hi,

Having followed the steps in the simple create through balena cloud / etcher process (https://www.balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/), I’m having serious trouble getting anything working on my Raspberry Pi 3. It seems as if there are no airplay / bluetooth etc services running. Target supervisor state lists the following:

{
“local”: {
“name”: “icy-lake”,
“config”: {
“RESIN_RESTART”: “3970960993419106”,
“RESIN_SUPERVISOR_DELTA_VERSION”: “3”,
“RESIN_SUPERVISOR_NATIVE_LOGGER”: “true”,
“RESIN_HOST_CONFIG_disable_splash”: “1”,
“RESIN_HOST_CONFIG_dtparam”: ““i2c_arm=on”,“spi=on”,“audio=on””,
“RESIN_HOST_CONFIG_enable_uart”: “1”,
“RESIN_HOST_CONFIG_gpu_mem”: “16”,
“RESIN_SUPERVISOR_DELTA”: “1”,
“RESIN_SUPERVISOR_POLL_INTERVAL”: “900000”
},
“apps”: {
“1677546”: {
“name”: “balena-sound”,
“services”: {},
“volumes”: {},
“networks”: {}
}
}
},
“dependent”: {
“apps”: {},
“devices”: {}
}
}

Supervisor status is:
Supervisor Status:
{
“api_port”: 48484,
“ip_address”: “192.168.1.64 192.168.1.238”,
“os_version”: “balenaOS 2.51.1+rev1”,
“supervisor_version”: “11.4.10”,
“update_pending”: false,
“update_failed”: false,
“update_downloaded”: false
}

Any advice / help gratefully received!

Rich

2

Hi Rich, thanks for reaching out. The target supervisor state doesn’t look right, can you check if there is a release in the “Releases” tab? Alternatively, you can try deploying by clicking the “Deploy with balena” button, and adding a device there. That should configure and deploy a release correctly for you, and once the device is up, the device will pick up the target changes and run balenaSound. If that doesn’t work for you, we can look into what went wrong.

4

Hi @sradevski,

Ah, I hadn’t seen the releases tab (not sure how I missed it…). There’s a failed release in there, log as below:

[Info] Starting build for balena-sound, user rich_okelly
[Info] Dashboard link: https://dashboard.balena-cloud.com/apps/1677546/devices
[Info] Building on arm03
[Info] Pulling previous images for caching purposes…
[Success] Successfully pulled cache images
[Info] Starting to build upnp
[Info] Starting to build airplay
[Info] Starting to build snapcast-server
[Info] Starting to build bluetooth-audio
[Info] Starting to build spotify
[Info] Starting to build fleet-supervisor
[Info] Starting to build snapcast-client
[Success] Successfully built service spotify
[Success] Successfully built service fleet-supervisor
[Success] Successfully built service airplay
[Success] Successfully built service snapcast-server
[Success] Successfully built service snapcast-client
[Success] Successfully built service upnp
[Success] Successfully built service bluetooth-audio
[Info] Uploading images
[Error] An error occured: (HTTP code 404) no such image - no such image: ea7c7fc6c5c7: No such image: ea7c7fc6c5c7:latest
[Info] Built on arm03
[Error] Not deploying release.

I’ve only ever tried the “Deploy with Balena” option, will try again and post back.

Many thanks,
Rich

5

Hi @sradevski,

Similar error again, this time tried deploying via the CLI, grateful of any advice on resolution that you can offer. Logs are below (I have the terminal output as well if useful):

[Info] Starting build for balena-sound, user rich_okelly
[Info] Dashboard link: https://dashboard.balena-cloud.com/apps/1677546/devices
[Info] Building on arm01
[Info] Pulling previous images for caching purposes…
[Success] Successfully pulled cache images
[Info] Starting to build spotify
[Info] Starting to build bluetooth-audio
[Info] Starting to build upnp
[Info] Starting to build snapcast-server
[Info] Starting to build fleet-supervisor
[Info] Starting to build snapcast-client
[Info] Starting to build airplay
[Success] Successfully built service snapcast-client
[Success] Successfully built service fleet-supervisor
[Success] Successfully built service spotify
[Success] Successfully built service airplay
[Success] Successfully built service snapcast-server
[Success] Successfully built service bluetooth-audio
[Success] Successfully built service upnp
[Info] Uploading images
[Error] An error occured: (HTTP code 404) no such image - no such image: 811e95dcfe0d: No such image: 811e95dcfe0d:latest
[Info] Built on arm01
[Error] Not deploying release.

6

Hi,
we are sorry for the inconvenience, we are currently seeing some builder issues and are working to fix them, could you please try the build a bit later and come back if the problem persists even after 24 hours?

8

Hi,

Thanks for the update, will try again later today and tomorrow if not working later. How long has this issue been present for (I experienced the same thing a couple of days ago, but have deleted the apps presuming it was an error on my part)?

Many thanks,
Rich

10

In case useful, the following lines in the terminal logs look like they could be a cause of an issue (or could be expected behaviour - not sure):

[snapcast-server] invoke-rc.d: could not determine current runlevel
[snapcast-server]
[snapcast-server] invoke-rc.d: policy-rc.d denied execution of start.
[snapcast-server]

…

—> Running in 5758c1b6abfa
[airplay] failed to export image: failed to set parent sha256:30616a1612dd85aab36f2432bc7f612fc43a6a01275252aa034cc749fffb61d4: unknown parent image ID sha256:30616a1612dd85aab36f2432bc7f612fc43a6a01275252aa034cc749fffb61d4
[upnp] invoke-rc.d: could not determine current runlevel

Best wishes,
Rich

12

Hey, we have been informed that this issue has been resolved and your builds should be working again.

14

@20k-ultra thanks! We’re in business, up and working!

I’m assuming that some form of internal alerts were triggered as a consequence of this underlying issue. And, having lost a fair few hours to this as I tried (unsuccessfully) trying different install set ups (32 vs 64 bit, different release versions that folk online seemed to have successfully set up on a Pi 3), may I make a feature request please that, in case of any issues such as this, users are notified of the issue (and what the impact may be) via the web interface?

That said, I appreciate the support offered on this forum, thank you!

Best wishes,
Rich

15

This is a good point and the current approach to knowing about errors would be to check our status page: https://status.balena.io/ which would contain any known issues that are ongoing. Having it highlighted in the dashboard is something to consider as well for users that are unaware we have this status page so I’ll be sure to bring it up.