Maybe I’m missing something, but I don’t understand how the QEMU pointer helps those of us that were using balenaos-in-container. We very specifically need it to run in a container for platforms like Neeve and Azure Stack Edge.
Seemed like we were really close to getting 3+ working (see Issue #60 ), which @klutchell pinned two weeks ago… so, why kill it off?
Apologies, I should have followed up after updating the README. We internally discussed the past progress around supporting balenaos-in-container for OS 3+, and found that we still had a ways to go with regards to getting it to work. We decided to proceed with QEMU as the sole supported option.
However, it seems there’s some context we’re missing around your use case, where QEMU is incompatible with Neeve / Azure Stack Edge. Could you describe it please? It’ll allow us to reevaluate our decision with a more complete picture of customer use cases.