Resin/balena name migration

aliasbits · August 21, 2019, 10:05am

Questions regarding resin/balena namespace cleanup

Where is https://files.resin.io/ relocated in the balena namespace in order to access
https://files.resin.io/images/intel-nuc/2.26.0%2Brev1.dev/kernel_modules_headers.tar.gz ?
What os/supervisor version supports balena equivalent of RESIN_SUPERVISOR_HOST RESIN_SUPERVISOR_PORT RESIN_SUPERVISOR_ADDRESS RESIN_SUPERVISOR_API_KEY?
What version of os/supervisor allow for named volume balena-data instead of resin-data in the docker compose file?

Info:
Page https://www.balena.io/docs/learn/develop/multicontainer/ is incomplete/misleading regarding resin/balena namespace and when it happend

robertgzr · August 21, 2019, 11:02am

hey @aliasbits the files.resin.io subdomain should still work, doesn’t it for you?

robertgzr · August 21, 2019, 11:09am

Looks like supervisor v7.22.0 introduced the BALENA_* env vars (1) and v7.23.0 brought in the io.balena.* labels (2)

(1): https://github.com/balena-io/balena-supervisor/blob/master/CHANGELOG.md#v7220---2018-10-17
(2): https://github.com/balena-io/balena-supervisor/blob/master/CHANGELOG.md#v7230---2018-10-18

robertgzr · August 21, 2019, 11:14am

Regarding named volumes, those can have arbitrary names, resin-data is a a remnant of how persistent storage worked prior to balenaOS v2.12.0 https://www.balena.io/docs/learn/develop/runtime/#persistent-storage

aliasbits · August 21, 2019, 11:15am

It still works, but unsure if files.resin.io will be deprecated at some point

aliasbits · August 21, 2019, 11:22am

Just to be sure. Will any named volume be persisted until installation of new application?

As of now we use ‘resin-data:/persistent’ in the docker compose to setup persistent storage

robertgzr · August 21, 2019, 11:41am

What balenaOS version are you running?

aliasbits · August 21, 2019, 11:51am

Right now we are using:
balenaOS 2.29.0+rev1 supervisor 9.0.1
balenaOS 2.39.0+rev3 supervisor 10.0.3

robertgzr · August 21, 2019, 11:54am

yes any named volume you define will be persisted across application and/or OS updates

CameronDiver · August 21, 2019, 5:41pm

Hey @aliasbits

When you move a device between applications, the volumes associated with the previous application will be removed. This means that any data stored in those volumes will be deleted.

Since supervisor v10, when you remove a volume from your docker-compose file, the volume is not removed from the device, and must be done explicitly. With supervisor versions earlier than this, removing a volume from the docker-compose file will also remove it from the device and delete the data.

Please let me know if you’d like some further clarification.