can't access with Container_IP:9080 or any other port

[jluc2808]

hello,
i run the last proxmox 5.3 on a x86 machin (core2duo 8500, 4Go Ram, wired ethernet, DD SATA: 156Go)
i just installed a new CT using debian-9.0-standard_9.5-1_amd64.tar.gz and after a successfull start i have sucessfully installed jeedom package from
https ://raw.githubusercontent.com /jeedom/core/master/install/install.sh
all the section and part have ran with successfull report

i have restarted the CT (as asked at the end of the installation) and get the CT running well

BUT: i can't connect to any apache2 web service using either the CT-name or IP address -
my CT is configured with ID: net0
Name eth0
bridge : vmbr0
Firewall : No
MAC adress: xxxxxx
IP address: dhcp (i find the IP address using ip -s -c -h a)

what is wrong ?
thanks for some help
best regards
jean-luc

 

[oguz]

Are the services running properly?

systemctl status apache2
journalctl -b -u apache2

Can you post your container config as well?

pct config CTID

 

[jluc2808]

return from systemctl status apache2

pache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/apache2.service.d
           `-privatetmp.conf
   Active: active (running) since Fri 2019-03-22 08:53:03 UTC; 2h 15min ago
  Process: 222 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
 Main PID: 499 (apache2)
    Tasks: 6 (limit: 4915)
   CGroup: /system.slice/apache2.service
           |-499 /usr/sbin/apache2 -k start
           |-532 /usr/sbin/apache2 -k start
           |-533 /usr/sbin/apache2 -k start
           |-534 /usr/sbin/apache2 -k start
           |-535 /usr/sbin/apache2 -k start
           `-536 /usr/sbin/apache2 -k start

Mar 22 08:52:59 docker-debian systemd[1]: Starting The Apache HTTP Server...
Mar 22 08:52:59 docker-debian apachectl[222]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Mar 22 08:52:59 docker-debian apachectl[222]: Setting ulimit failed. See README.Debian for more information.
Mar 22 08:53:03 docker-debian systemd[1]: Started The Apache HTTP Server.

return from journalctl -b -u apache2

-- Logs begin at Fri 2019-03-22 08:47:58 UTC, end at Fri 2019-03-22 11:10:03 UTC. --
Mar 22 08:52:59 docker-debian systemd[1]: apache2.service: Failed to reset devices.list: Operation not permitted
Mar 22 08:52:59 docker-debian systemd[1]: apache2.service: Failed to set invocation ID on control group /system.slice/apache2.service, ignoring: Operat
Mar 22 08:52:59 docker-debian systemd[1]: Starting The Apache HTTP Server...
Mar 22 08:52:59 docker-debian apachectl[222]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Mar 22 08:52:59 docker-debian apachectl[222]: Setting ulimit failed. See README.Debian for more information.
Mar 22 08:53:03 docker-debian systemd[1]: Started The Apache HTTP Server.

resultat PCT config 101

arch: amd64
cores: 1
hostname: docker-debian
memory: 1024
net0: name=eth0,bridge=vmbr0,hwaddr=76;DC:82:DE:AB:22,ip=dhcp,type=veth
postype: debian
rootfs: local-lvm:vm-101-disk-0,size=8G
swap: 512
unprililedged: 1

 

[oguz]

Looks like apache is working as expected. The ulimit error can be ignored.

I guess you're using docker on this CT? For nested containerization (LXC + docker or LXC + systemd nspawn etc.) you should enable the "Nesting" feature for the CT. This can be done in the GUI under container options or you can add

features: nesting=1

to the container config.

Also, please check if you have a firewall enabled (on Proxmox settings or in the container itself). Maybe that's why you can't reach the services

If not, the output from

ss -l

can be also useful in debugging any issues with services.

 

[jluc2808]

the result is the same using container_IP:9080 but
if i start with just container_IP no port it's OK
unbelievable !!!!

thanks a lot