i'm using a vps with openvz and FUSE wasn't enabled, i'd contact the support team and they enable it instantly (reboot required). i don't know how they enable it but i can confirm that fuse could work in openvz. with google i found this, hope it helps. https://openvz.org/FUSE
What proxmox version are you using? For 3.4 or lower, you can follow this tut: https://openvz.org/Bind_mounts
Just mount /var/lib/vz/private/110/path/to/folder/in/container to /var/lib/vz/private/105/path/to/where/you/want/the/folder/mounted and done.
For example, this is my /etc/vz/conf/107.mount file, this one mounts various files from different containers (105 and 104 for instance) to 107 for it to use:
#!/bin/bash source /etc/vz/vz.conf source ${VE_CONFFILE} mkdir -p ${VE_ROOT}/mnt/domain1 mkdir -p ${VE_ROOT}/mnt/domain2 mkdir -p ${VE_ROOT}/mnt/domain3 mount -n --bind /var/lib/vz/private/105/var/www/vhosts/domain1.com/ ${VE_ROOT}/mnt/domain1 mount -n --bind /var/lib/vz/private/105/var/www/vhosts/domain2.com/ ${VE_ROOT}/mnt/domain2 mount -n --bind /var/lib/vz/private/104/var/www/vhosts/domain3.com/ ${VE_ROOT}/mnt/domain3 mount -n --bind /var/lib/vz/private/105/var/www/vhosts/domain4.com/ ${VE_ROOT}/mnt/domain4
That's not allways true. Some providers allow using tun/tap on openvz virtual server. If you have a good option for openvz vps just ask the provider, if they allow a private openvpn service on their virtual server.
To clarify, I talk of containers not in the newer Docker/Podman context, rather the definition from OpenVZ themselves:
Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files.
So rather than pulling one container per app, an OpenVZ container is more like a VM as I understand it.
Interesting. I have had none of those 3 issues with my Proxmox 4 and my Ubuntu containers.
SSH server comes pre-installed, even in the ~75MB minimal template option. They shut down perfectly as you would expect. And I can mount CIFS from inside container just fine.
I got my container templates from here though:
https://openvz.org/Download/template/precreated
I know they are openvz templates, but they work perfectly for me with Proxmox 4 LCX. I've used the 14.04 and the 15.10.
If you are using OpenVZ containers to use as VPN server you need to do some extra steps on the host node to make VPN works. First of all, you need to load some more modules for IPtables of the container to do the work correctly, this is modified, If i recall correctly, from the config file of that container, something along these lines should be OK: IPTABLES="iptable_nat ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_LOG ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_state ipt_conntrack ipt_helper iptable_nat ip_nat_ftp ip_nat_irc ipt_state iptable_nat"
You also need to make the tun0 device visible to the openvz container, make sure you load the tun module (modprobe tun) and you make it visible to the container as a normal /dev/ entry: CTID=101 vzctl set $CTID --devnodes net/tun:rw --capability net_admin:on --save
If I recall correctly this is what I did to make openvpn work on vz containers unders proxmox 3.4, anyway, this link should be useful enough to get it runing: https://openvz.org/VPN_via_the_TUN/TAP_device
I dont fully understand the question but may this help's:
proxmox can deploy VM's, OpenVZ is very straight forward, you can download VM templates here: https://openvz.org/Download/template/precreated
On a blank debian wheezy just follow this guide for proxmox setup. https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy
Backup and Restore - Proxmox VM's https://pve.proxmox.com/wiki/Backup_and_Restore
> you can't run openvz using lxc modules or run openvz with an unmodified kernel like kvm.
You've been able to for a while now: https://openvz.org/Vzctl_for_upstream_kernel
Granted, you're missing many of the more advanced openvz features that haven't made it upstream yet, but the set of patches necessary has been shrinking rapidly over the last few years.