Displaying IP of container in GUI?

jeffsui

Member
Dec 11, 2022
7
10
8
So for VMs (probably running the qemu-agent) I'm able to see the IP listed in the summary tab of the PVE gui. For containers the best i can find is go to the network tab, look at the Mac address and then query my router to find the IP.

VM Status:

1673396183389.png
Container Status
1673396329334.png


Container network tab:
1673397201674.png

Is there a way to get the IP from the GUI or is this not possible?


Thanks!
 
I'm having the same issues though I think I know my IP address I'm struggling to connect to Portainer for the first time on installing it. It gave me an IP address and was told to add:9000 at the end of it but it's not loading the browser or finding it so not sure if it is the correct IP address or the correct port. Any clues or help me great!
 
  • Like
Reactions: YFanha
over 4 years and GUI still not uptated to pull details from
lxc-info -n <CONTAINER ID>

I guess at least it shows MAC so that will help me when identifying in mikrotiks gui
 
  • Like
Reactions: darmach
Thank you so much. It makes life easier with a very simple solution.
Maybe Proxmox can re-place the IP from the TAG in the GUI.
Seems small development effort to me, but I may be wrong, I'm not a coder.
 
This is the answer, and there is are good comments in the bug report. It would be great to be able to see the IP address assigned via DHCP to the container without having to know a command line command.
As paid proxmox customer I would like to ask when this issue will be addressed. This is really annoying and makes ansible inventory plugin a bit unusable...
 
  • Like
Reactions: darmach
I know that's not what's asked initially, but in my case to remember the IP of the VM/containers that I want to have a fixed IP I set the static DHCP in the router like:
CT/VM ID -> IP
100 -> 192.168.1.100
101 -> 192.168.1.101
and so on...

obviously this doesn't work for the question: i start a new container, i want to know its IP without assigning it a static IP... but it's something..

(I do that in this way because I prefer to set all the static ips of my network in a single place if i need that, so i leave dhcp for all the containers in proxmox)
 
Last edited:
in the host shell i can use: pct exec <ctid> ip a and look for the IP there, but agree this HAS to be built in somehow :|
 
Since there isn't exactly fierce competition in the "tag LXC containers with IP addresses" category, I hope you don't mind if I throw in my two cents.

I wrote this script because I was missing a few key features in lxc-iptag.

The most important one was the ability to conveniently define ignored IPs — both as individual addresses and as entire ranges.

Another issue was that after shutting down an LXC container, the tags would simply disappear. I wanted to have control over what happens in such cases — now you can choose one of three options. By default, the tag stays, but changes color.

You can define separate colors for active and inactive (last seen) IPs. It's also possible to enforce where the tags should be added and displayed — either at the beginning or at the end. There's also dynamic IP-based sorting, position tracking, and more.

https://github.com/MorsStefan/proxmox-ip2tag
 
I'm having the same issues though I think I know my IP address I'm struggling to connect to Portainer for the first time on installing it. It gave me an IP address and was told to add:9000 at the end of it but it's not loading the browser or finding it so not sure if it is the correct IP address or the correct port. Any clues or help me great!
For what it's worth for those (like me) reading this later, as of 2025, Portainer changed their default port to 9443

Source: https://solid-future.com/docs/porta... web-based interface, which runs on port 9443.