You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resin/resinos:2.95.12_rev1-genericx86-64-ext is a unified release so there is no distinction between production & development images. The image will be configured appropriately if a user downloads it using the SDK/CLI/web. If they use the hostapp it will be configured with whatever their config.json states for developmentMode, as the hostapp does not include the boot partition.
The config.json that is copied to the boot mount should have developmentMode: true. The config.json is downloaded from the balenaCloud dashboard—this needs to be a development version.
Also, it should stop using dockerhub and use bh.cr instead
Current workaround: Use balenaos-in-container as is for balenaOS releases before v2.85
The text was updated successfully, but these errors were encountered:
resin/resinos:2.95.12_rev1-genericx86-64-ext is a unified release so there is no distinction between production & development images. The image will be configured appropriately if a user downloads it using the SDK/CLI/web. If they use the hostapp it will be configured with whatever their config.json states for developmentMode, as the hostapp does not include the boot partition.
It currently hardcodes a
-dev
to images (as seen in Dockerfile.template#L6 )The config.json that is copied to the boot mount should have
developmentMode: true
. The config.json is downloaded from the balenaCloud dashboard—this needs to be a development version.Also, it should stop using dockerhub and use bh.cr instead
Current workaround: Use balenaos-in-container as is for balenaOS releases before v2.85
The text was updated successfully, but these errors were encountered: