Start unmanaged container from the Web UI?

[raboof]

Hi,

I have a custom-built LXC container (not based on any of the distro's explicitly supported at https://git.proxmox.com/?p=pve-cont...e0649d1779f4e709c207dcecf4ed62cf4;hb=HEAD#l18 ).

I have a non-root PAM user, and it seems elegant to not require root.

When I start the container from the Web UI, it fails because it cannot detect the OS. I read https://forum.proxmox.com/threads/i...reate-unable-to-detect-os-distribution.63323/ and it seems the solution is to run the container as 'unmanaged', but I don't see how to do this from the Web UI.

Is this possible?


Kind regards,

Arnout

 

[t.lamprecht]

Hi,

I have a custom-built LXC container (not based on any of the distro's explicitly supported at https://git.proxmox.com/?p=pve-cont...e0649d1779f4e709c207dcecf4ed62cf4;hb=HEAD#l18 ).

How did you created this CT in Proxmox VE? As if you say we don't support your distro (what is it?) our creation code path should error out.

When I start the container from the Web UI, it fails because it cannot detect the OS. I read https://forum.proxmox.com/threads/i...reate-unable-to-detect-os-distribution.63323/ and it seems the solution is to run the container as 'unmanaged', but I don't see how to do this from the Web UI.

Is this possible?

Can be, but we'd need some more details about what runs in the CT.

 

[raboof]

> How did you created this CT in Proxmox VE?

I created the image using 'nix' (all the details are at https://github.com/raboof/mastodon-bot-nix, though I'm not sure they're relevant here)

I have tested running the container on a system with 'lxd', there it works.

I uploaded the tarball into proxmox with the Storage section of the Web UI.

> what is it?

There isn't really a distro inside the image, it's just some Linux executables, scripts etc. The packages are derived from NixOS.

 

[t.lamprecht]

> How did you created this CT in Proxmox VE?

I created the image using 'nix' (all the details are at https://github.com/raboof/mastodon-bot-nix, though I'm not sure they're relevant here)

I have tested running the container on a system with 'lxd', there it works.

That's not answering how you created the Container in Proxmox VE that's how you created the rootfs, albeit that's also relevant.

I uploaded the tarball into proxmox with the Storage section of the Web UI.

So you have not yet a container configuration? That makes more sense. So you will have to use the "unmanaged" ostype, as anything else will fail.

Use the CLI for that, e.g., the following command should get you quite in the right direction:

pct create 200  /local/path/to/rootfs.tar.gz --cores 2 --net0 name=eth0,bridge=vmbr0 --unprivileged 1 --start 1 --features nesting=1 --ostype unmanaged

Adapt vmid if 200 is not free (or desired), the path to the rootfs.tar can be either a fully local path or using the Proxmox VE volid (see pvesm list <storage> for how to get that).

You then need to handle networking inside the CT "yourself", but I guess nixOS handles that just fine.

There isn't really a distro inside the image, it's just some Linux executables, scripts etc. The packages are derived from NixOS.

"some Linux executables, scripts etc." that sounds like being quite similar to what most Distros consist of

 

[raboof]

That's not answering how you created the Container in Proxmox VE that's how you created the rootfs, albeit that's also relevant.

Ah, right, sorry - I don't have all the nomenclature internalized just yet, I'll try to be more careful

Use the CLI for that

My PAM user doesn't have root, so AFAICS I cannot use the pct command-line tool (it returns "please run as root").

So you will have to use the "unmanaged" ostype, as anything else will fail.

Thanks for confirming. I tried to create the CT with the 'Create CT' button at the top-right of the web UI, but didn't find an option to set the ostype there. Did I miss it, or should I arrange root access?

You then need to handle networking inside the CT "yourself", but I guess nixOS handles that just fine.

We'll see

"some Linux executables, scripts etc." that sounds like being quite similar to what most Distros consist of

Heh, yes, of course

 

[shodan]

Hello

How can the user set ostype to unmanaged
when using the web interface to create an LXC container that is not recognized ?

This is also an issue in

https://forum.proxmox.com/threads/openwrt-lxc-installation-error.106991/
https://github.com/tteck/Proxmox/discussions/962

I have tried to create it manually, even with advanced check, I could not find it

And it gives this error




However, by the command line it works just fine

root@proxmox:~# pct create 1003 local:vztmpl/openwrt-amd64,23.05,default.tar.xz --arch amd64 --cores 4 --memory 1024 --hostname vpn  --net0 name=eth0,hwaddr=DE:AD:BE:EF:01:95,ip=dhcp,ip6=manual,firewall=0,bridge=vmbr0 --net1 name=eth1,hwaddr=DE:AD:BE:EF:01:96,ip=dhcp,ip6=manual,firewall=0 --rootfs local-lvm:2 --features nesting=1 --unprivileged 1 --ostype unmanaged
  WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "vm-1003-disk-0" created.
  WARNING: Sum of all thin volume sizes (<1.64 TiB) exceeds the size of thin pool pve/data and the size of whole volume group (<446.13 GiB).
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: eac14a05-14d5-4376-9b94-602db689bc2a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912
extracting archive '/var/lib/vz/template/cache/openwrt-amd64,23.05,default.tar.xz'
Total bytes read: 14315520 (14MiB, 62MiB/s)
root@proxmox:~#

 

[t.lamprecht]

There is currently no way to enforce a container being "unmanaged" if created from the web UI, maybe we could expose that as advanced setting, feel free to open an enhancement request over at: https://bugzilla.proxmox.com/