Not really. It creates more work and abstraction from the actual use case.
There are always issues that exist within a container that do not exist outside of it, we have enough of this sort of stuff with our own solbuild such as some builds and unit tests failing only when ran inside it.
If something was found to be broken the next step would be, does it fail when run normally? So now I tested it twice and potentially deal with investigating why it hates distrobox and if that is our bug, theirs or some unknown limitation of the env with that specific app.
