@Richard Since i have the same issues it sould nearly the same like in @OliverB's case:
/etc/network/interfaces (CT)
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.10.10.2
netmask 255.255.255.0
gateway 10.10.10.1
/etc/resolv.conf (CT)
# ---...
@manu So, docker is away until the problems solved - since docker seems not to be the problem. I tried a lot and nothing helped. i compared the configuration with this of my personal instance with no luck.
@manu You're right, that would be better, but since it's already a "virtualized root server" i'm not abled to create KVM machines, only containers. On the other hand @OliverB seem not having docker and running into the same issues. I'm willing to test remove the docker installation restart the...
I've used the dns tab on the ui which generated following content in the container
# --- BEGIN PVE ---
domain.tld
nameserver 80.237.x.y
nameserver 80.237.x.z
# --- END PVE ---
This are the nameserver from the hosting provider
Hello,
I currenty facing network problems with the virtual adapter for the container network.
Here is my network config
/etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 5.35.x.y
netmask 255.255.255.0
gateway 5.35.x.y...
seems to be a little bit frustating since i'm not sure how perfomant qemu is (in comparision to an lxc container or the host system). What are the issues that you recommend to install docker inside an vm instead on the host system?
Hi tom, thanks for fast response. Do you mean (K)VM or LXC container? Since the System is already virtualized Server (KVM) it's only possible to create LXC container. Moreover we want to use Portainer for administation of the docker container. There is already another thread with Docker in LXC...
Hello,
I've currenty setup another proxmox instance, which has some special needs.
Since we have heterogenous systems (existing containers) and new docker(-compose) based solutions we try to get them all on one system. Therefore i installed a fresh proxmox system. The second step was to install...
since i've not seen an bind example with nfs, is this the correct syntax for the container:
lxc.aa_profile: unconfined
lxc.mount.entry: 10.0.2.20:/var/atlassian var/atlassian nfs bind,create=dir,optional 0 0
Dec 13 09:57:22 proxmox kernel: [736791.256106] device veth222i0 entered...
ok, thats sounds logical
mmh, can you explain this more detailed? what do i have to to on the nfs server and what on the client? what's the todos on the host (proxmox)?
Hello,
I've multiple lxc containers sharing one directory on a nfs server on another container.
While manual mounting is working, mounting via mount.point.entry on the nfs client seem to be not working.
NFS-Server: 10.0.2.20
NFS-Client config
arch: amd64
cpulimit: 1
cpuunits: 1024
hostname...
So
i've simly had to create a directory on node and add the to lines to container config to mount a from directory into the container?
The containers share a private network not including the proxmox node so a "classic nfs share" is not possible.
Sorry for the late reply:
i finally managed to get the network work as expected (some days before your post, as i said, i'm sorry). So here is what i've did:
netwotrk interfaces on proxmox
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 188.68.49.XX...
Hi,
i try to do the same like you. If I'm not wrong, you create mount from container to proxmox?
Do you know if mount from lxc to lxc possible and how it should looks like?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.