Felipe Lalanne

Can't say I remember that @20k-ultra

Managed to replicate this issue. It will happen if the `balena-logo-default.png` has the same value as `balena-logo.png` and the `BALENA_HOST_SPLASH_IMAGE` variable. The issue is here https://github.com/balena-os/balena-supervisor/blob/8750951521ee3b945e3eb5f5fe10c467cb97adf8/src/config/backends/splash-image.ts#L108-L112 the code above will...

Actually is not that easy, because most existing devices do not have a splash, that means when updating to a supervisor with splash support, that would get the logo deleted....

@alexgg I don't think this applies, the supervisor never mounts `/dev` for user containers. Or do you mean for the supervisor itself?

@alexgg I believe if the device doesn't exist the engine won't let you start the container. Removing the device won't remove the node in the container `/dev`, so that will...

> Ideally what we would want would be for applications to be able to specify a non-existent /dev/ device and flag it as hotpluggable in the compose file I see,...

This requires an API change first, as the supervisor does not receive the version information via the target state

@bbugh regarding security. Using the `io.balena.features.balena-api` [feature label](https://docs.balena.io/reference/supervisor/docker-compose/#labels) will give a service access to the device API key, which is what the supervisor uses to communicate to the API and...

@cywang117 remember to take a look at this when you get a chance

Will need to refactor this, I had not considered that, because of the git workflow, in a multi-app world you could have two apps pointing to the same release commit....