

Lxc doesn’t use oci images?
https://github.com/lxc/lxc/commit/0ef43a5c1d635835950335375f0dd71bf1abe384
It does.
Nope. I don’t talk about myself like that.
Lxc doesn’t use oci images?
https://github.com/lxc/lxc/commit/0ef43a5c1d635835950335375f0dd71bf1abe384
It does.
Why bother asking for help if you’re not going to do the bare minimum of bringing us up to speed on what you’re running and how it’s configured. Just to be a complete jackass and “block” everyone the moment they ask for any of that information in order TO HELP YOU.
To this point the only facts we know…
Your running docker. You added two containers. One of which might be Hanabira. That were run via docker compose. SSH is working, but not… because you didn’t actually explain that well at all.
That’s it. That’s all you’ve provided and I had to literally read EVERY thread to find that. That’s all we got. Nobody can help you. And with people outright asking you for more, and your hostility in return to those trying to help you. Nobody else will want to help you. Including me.
Good luck. But I wanted you to know that you’re the jackass here.
It’s mildly funny though that you live up to your .ml instance preconceptions.
14% ownership is ownership. Not just “big investor”. It’s not big enough ownership to pull unilateral changes, but when someone owns 14% of your company they do sit at the big boy table.
If you’re using just raw LXC it’s easy…
lxc-create <<name>> -t oci -- --url docker://alpine:latest
Will spawn an alpine docker container for instance.
If you’re using something like proxmox though, it’s a little more annoying since there’s some work to get proxmox to add it to it’s container list.