Add LXC containers (from Proxmox) like docker containers

[LuciDuki]

Description

Hi,

I wanted to ask if it is possible to add LXC containers (from Proxmox) like the docker containers. Maybe I overread something and this is already possible, then i would appreciate a link where i can get the information for that.

Otherwise, if this is currently not possible, can this feature be added?

Best Regards
Lucas

Other

No response

[jagadam97]

@LuciDuki
This is already supported by proxmox widget. Please follow the documentation from https://gethomepage.dev/en/services/proxmox/
Here you can see my widget showing the info.

[LuciDuki]

Hi, already noticed that. But I want to see the detail of a specific lxc container. like in the docker (cpu, memory ,etc of the lxc container)

Best Regards

[cclarke99]

Jumping in here to support this request. While I love docker and it's capabilities, I run a lot of my services in LXC containers on my Proxmox cluster and would love to be able to see their status like we can today with docker containers on Homepage.

[james-prince]

Would be great if we could get some sort of LXC stats, either LXC specific container widget showing things like CPU/Mem for an individual container, or some sort of LXC / VM auto listing like we have for docker containers.

[paulkakell]

I also wanted to request this feature.

[dukeseb]

i would support anything that would give more information about anything on my proxmox system.

[FriendlyNGeeks]

Just to confirm with everyone on this thread. We are looking for a drop-in solution to mirror the functionality of the Docker Proxy implementation for Proxmox. Allowing users to define lxc/vms in a separate yaml and pull simple information from the Proxmox api endpoint as follows: https://localhost:8006/api2/json/nodes/$NODE/lxc . This returns a data:array of all lxc on that node running or not. A object mapping would be needed to reassign the information into a object key:value by either name/vmid/pid which could then in turn be used in the services.yaml using tag of lxc: instead of the docker equivalent of server: . I will go on to say the approach of grabbing the json once from Proxmox and sorting out container info in javascript seems to be a better solution then sending multiple request for each lxc on the datacenter.