Search results

Same issue here! Moreover modifying /etc/network/interfaces: # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or...

Great! Adding this repo: deb http://download.proxmox.com/debian/pve buster pve-no-subscription Solved the issue! Many thanx!

I use ProxMox VE 6.1-7 that seems to be the last version. Consider that I'm a free user so I don't have the right to access some repositories where the patch may be distributed... By the way moving the file to the /var/lib/vz/dump doesn't solve the issue.

Hi, unfortunately I have some issue following this example and I need a more detailed informations (sorry! ;-) ) The situation is that I backed up some LXC container from an experimental in-house server into the datacenter machine both with the same proxmox ve; on the production machine I use...

Yes, both containers are on the same host (it's my server); well we know that we have traffic between the two containers also when trying to access to MariaDB; now the question is: Why MariaDB appears to be closed from outside BUT the port is open when nmapping from the same containers to the...

As you correctly noted the packets don't leave the NIC and the machine is behind a firewall; but philosophically seems to me a correct choice to separate a "container only" network and a network attached to a WAN... At the time vNICs are free of charge... :-D

Another idea I had, it's related to another issue I had on a ProxMox infrastructure based and a VM based on Ubuntu 18.04: After an update the networking was down. After writing to the Contabo support (that hosted this VMs and that uses ProxMox too) they reported a "more common Ubuntu 18...

Yes! Both containers have 192.168.1.0/24 and 192.168.10.0/24 in two NICs: ETH0 and ETH1 bond on VMBR0 and VMBR1 respectively. VMBR0 bond to enp0s8 then to the WAN. VMBR1 only local to have communication between containers.

Not exactly. Both containers has a second VNIC on 192.168.10.0/24 network... I suppose (and frankly speaking I hope!) that when querying from the test container to the MariaDB container both use the 192.168.10.0/24 network that don't need routing. But just to be clear, MariaDB on it's container...

Todor, great news! Thank you in the meanwhile! We have traffic. As you suggested: CT100 # ip route list default via 192.168.1.1 dev eth0 onlink 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.150 192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.13 CT105 # ip...

Previously the firewall was enabled but the rule's table was empty. Now I completely disabled the firewall. I tried an `nmap` from the host (host ip address is 192.168.1.210 - so same subnet of the containers) to the CT100 container but the port 3306 is closed. However an `nmap` from the host...

Hi all, I've a network related issue. On ProxMox VE 6.1-8 I have several containers, all based on debian 10.3. All containers are connected via two bridges: - vmbr0 connected to the physical ethernet port enp0s8 for outside connection, with address 192.168.1.210/24; - vmbr1 internal to all...

It seems that the only solution is: Don't use container, use a VM instead. FPG

Hi Fabian thank you for your answer. I've noticed that the syntax to achieve the result is: pct set 103 -mp0 /host/dir,mp=/container/mount/point (note the position of mp= to designate the mountpoint into the container) This is equal to what stated into the wiki. As user I strongly suggest you...

Hi everybody, I'm stuck about mounting an host directory into an LXC container; the directory has to be read/write and the container is unpriviledged. Some googling leads me to bind mount points but the instructions here doesn't looks very clear for me; moreover issuing a command like: pct set...

I don't know why, the ssh connection gets interrupted! Now the issue is solved.

Hi all, this is what's happens while I'm migrating an LXC container from one node of my datacenter to another: 2020-03-02 22:20:13 starting migration of CT 101 to node 'vmhost00' (192.168.1.210) 2020-03-02 22:20:13 found local volume 'local:101/vm-101-disk-0.raw' (in current VM config)...

Same issue here. Working on a test server with KFSN5-D motherboard and two six core opteron, 16Gb RAM. Debug mode don't provide any additional info; just hangs with the same message. Trying to install on top of a working Debian distro. Please indicate on your dox which distro is supported...

Ok, so opposite to what said by @Stefan_R, no customer task can be performed on ceph cluster on your platform. Is this correct? Sounds clear for me. But the question is another: The question is: Do you know who provide a qualified support on ceph?

Hi Stefan, thank you for your answer. Of course we use one ceph cluster only for customer tasks and another ceph cluster only for VMs; I hope is possible to have several clusters declared on one datacenter. Thank you for the clarification; who we have to ask for enterprise support for ceph...