eclipse/zenoh:1.5.1 worked eclipse/zenoh:main did not

[nargetdev]

for ./build/examples/z_pub and ./build/examples/z_sub the eclipse/zenoh:main docker image does not work... immediately fails as

./z_sub
Opening session...
Unable to open session!

use tagged image eclipse/zenoh:1.5.1 ... and life gets better

>> [Subscriber] Received ('demo/example/zenoh-pico-pub': '[ 141] Pub from Pico!')
>> [Subscriber] Received ('demo/example/zenoh-pico-pub': '[ 142] Pub from Pico!')
>> [Subscriber] Received ('demo/example/zenoh-pico-pub': '[ 143] Pub from Pico!')

────────────────────────────────────────────────────────────────────────────────────
Putting Data ('demo/example/zenoh-pico-pub': '[ 124] Pub from Pico!')...
Putting Data ('demo/example/zenoh-pico-pub': '[ 125] Pub from Pico!')...
Putting Data ('demo/example/zenoh-pico-pub': '[ 126] Pub from Pico!')...
Putting Data ('demo/example/zenoh-pico-pub': '[ 127] Pub from Pico!')...
Putting Data ('demo/example/zenoh-pico-pub': '[ 128] Pub from Pico!')...

[github-actions]

PR missing one of the required labels: {'ci', 'internal', 'enhancement', 'documentation', 'new feature', 'dependencies', 'breaking-change', 'api-sync', 'bug'}

[gmartin82]

Thanks for your contribution, but the README is correct in that when working with a checkout of Zenoh Pico main, then eclipse/zenoh:main should be used.

When working with a tagged version of Zenoh Pico, we'd recommend using the corresponding version of the Zenoh router (which you have done in this case).

[nargetdev]

Use main is not at all obvious.

As another note - although in the end it is not many steps to get zenoh-pico running in platformio (on my ESP32 devices) it took me many hours figure out - I think a few more "idiot proof" instruction sequences will help launch this project.

[nargetdev]

https://github.com/nargetdev/zenoh-pico-example-platformio-arduino