My first guess is that there is some specific privileged required to run inside a default unprivileged container.
I did a quick search for the fix you are referring to, but nothing jumped out at me as what you were referring to. So without knowing exactly what the Docker fix entails I can't be sure, but there are reasonable odds that it is relevant to the issue you're hitting.
For what it's worth, my testing suggests that our appliance works fine in a full VM (installed from ISO). If you could share the link you're referring to, I'll have a look ASAP and see if it makes sense in the context of LXC. Either way when I get a chance I'll have a quick look myself and see if I can reproduce the issue running under LXC.
As a complete aside, Docker and LXC are very similar containerization implementations. Docker actually started life as LXC - just configured a little differently. Over time they have somewhat diverged, but the main difference is still the use case, rather than the technology. As you likely know, LXC provides full OS containerization, so more or less has a full OS (with some exceptions which leverage the host). As you also likely know, Docker is usually used as single application containerization. However under the hood, Docker still includes an OS, it's just the minimalist possible OS to run the desired app - plus any other dependencies.
Did you try the Docker fix?
My first guess is that there is some specific privileged required to run inside a default unprivileged container.
I did a quick search for the fix you are referring to, but nothing jumped out at me as what you were referring to. So without knowing exactly what the Docker fix entails I can't be sure, but there are reasonable odds that it is relevant to the issue you're hitting.
For what it's worth, my testing suggests that our appliance works fine in a full VM (installed from ISO). If you could share the link you're referring to, I'll have a look ASAP and see if it makes sense in the context of LXC. Either way when I get a chance I'll have a quick look myself and see if I can reproduce the issue running under LXC.
As a complete aside, Docker and LXC are very similar containerization implementations. Docker actually started life as LXC - just configured a little differently. Over time they have somewhat diverged, but the main difference is still the use case, rather than the technology. As you likely know, LXC provides full OS containerization, so more or less has a full OS (with some exceptions which leverage the host). As you also likely know, Docker is usually used as single application containerization. However under the hood, Docker still includes an OS, it's just the minimalist possible OS to run the desired app - plus any other dependencies.