Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

In this Discussion

New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Systemd-nspawn inside OpenVZ with Networking

Hi,

I am currently testing out the systemd-nspawn containers running inside OpenVZ with 2.6.32-120+ kernel.

The systemd-nspawn on Debian 8 is able to function correct to create a separate container running CentOS 7.

The problem I am facing now is the network setup for the container.

I tried veth it is not working, OpenVSwitch with Tap interface is not working either.

Anybody tried such setup before?

Thanks in advance.

Comments

  • You can either disable network namespace and all your container instances would use host network, or you can ask OpenVZ host provider to activate any supported by systemd-nspawn modules like veth.

  • WSSWSS Member

    Reinstall wheezy, and think about what you've done!

Sign In or Register to comment.