Almost right
vmbr1 shoud use the internal vrack IP not the range one (the local IPs you use to create the cluster ... but it seems you don't have one ?)
In my case it's a 172.16.x.x IP
In OVH manager, link your range(s) to the vrack
Then assign an ip from the range to the CT but :
- not...
I've a couple of containers running Debian 10 and certbot installed via snap
Since a couple of weeks, certbot is not working anymore. Last certificate generation is around December 22nd and it fails to renew (and yes we are the 21st ... 3 months later)
certbot renew
aa_is_enabled() failed...
I experience the same behavior
(still) Proxmox 6.4 on ZFS and LXC containers
Any operation in Docker is really slow and disk usage is growing
Building images takes hours and I got time out on starting containers in a stack so I have to start them several times.
So, thx, now I know that Docker...
Range is assigned to the vrack.
Vrack is working across DCs and countries.
https://www.ovh.com/fr/solutions/vrack/
It should work (must work according the doc)
Tested and it works very well !
I had to change the configuration of my vmbr1 bridge on the host and be careful as we can't have 2 different gateways in the same time on a container
will write a blog post about this and will referenced it here later
In brief:
- need an IPs range (not...
Hello. You can certainly move the FO IP from one host to the other manually using the OVH manager. That's how I work since years.
I've read it's possible to make this automatic using the OVH API and/or using Ripe IP range and using a script to send some arp packages. But I've never investigate...
Hi,
I've a cluster of 5 Proxmox 6 hosts (I know, I've to upgrade them to v7)
since years on these hosts, I was able to add new veth on containers using the GUI and get the IP up and running on the container.
Today, when I add the veth (let say eth1, with its mac address, the ipv4/32 and the...
Hi
I got the following error messages while doing snapshots on my Debian 10 running container
failed to open /snap/core/11187: Permission denied
failed to open /snap/core/11167: Permission denied
failed to open /snap/certbot/1201: Permission denied
failed to open /snap/certbot/1150: Permission...
Amazing @Fabian_E, it's certainly a major improvement (for me at least :-) ) It's still 2 cron per CT but it would be really useful !!
Another improvement would be to be allow to specify multiple vmid and/or "all CT except these ones" (like vzdump with the --all and --exclude parameters). But...
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.