[pve-devel] [PATCH container] lxc: fall back to 'unmanaged' on unknown ostype
Arnout Engelen
arnout at bzzt.net
Mon May 18 09:31:54 CEST 2020
On Mon, May 18, 2020 at 9:10 AM Thomas Lamprecht
<t.lamprecht at proxmox.com> wrote:
> On 5/17/20 11:03 PM, Arnout Engelen wrote:
> > AFAICT the 'create CT' web UI does not currently allow setting the ostype.
> > This of course could be changed/fixed, but the auto-detection that is already
> > there seems nice. I haven't used the API yet, and wanted to avoid using the
> > CLI (which requires root) where possible (though it looks like I'll have to
> > compromise there to get access to some features anyway ;) ).
>
> From our POV it's a feature, we support a set of distributions which we can all
> detect in a sane way. All unsupported cannot really get made to work easily over
> the web-interface anyway.
Yes, I agree detecting 'traditional' distributions in a CT and
'actively' supporting
them is definitely a useful feature.
> For what specific use case do you want this? What would be running in the CTs?
> Maybe it's easier to add support for that distro?
My CT is not really directly based on a distro, the /sbin/init just executes the
program I'm interested in running. I had tested this CT on another, non-proxmox
machine with lxc/lxd where it ran fine. Adding an /etc/os-release would not
be a huge deal, but the experience would be much nicer when it'd work without
additional changes - so I'm trying to help make that happen ;).
Kind regards,
Arnout
More information about the pve-devel
mailing list