openvz using the openvzdebian-7-turnkey-fileserver_13.0-1_amd64

I personally use the OVZ templates a lot, for both my personal testing and production (personal and professional). I use them on ProxmoxVE (open-source Debian based hypervisor which supports both OVZ and KVM) though rather than on vanilla OVZ. I recall that initially there were some issues running the first official TKL OVZ release on vanilla OVZ but that was a long time ago now and AFAIK they have all been resolved.

The patch you link to was my initial efforts to port TurnKey to run as an OVZ container. It was a TKLPatch which converted an appliance ISO to an OpenVZ template.

So short answer is that the templates that you link to on SourceForge should all just work!

ahh I got it running and then found some more road blocks so i edited my post .. for thous reading this above and wounder i was asking if I need to apply some patches.   Thank you for your quick responce.

I have it humming along but it seems it needs some tweeaks to get it operational.

if I could add users  or figure why it will not let me add users.

It looks super simple in youtube videos and that i might have a bug

is there a fix.

note I edit the post above and posted  the errors I have and will give any info  anyone needs to help me lick this issue. really want to try this out!

ok got the upgrade to work.. ssh in to the root@yourip
then

cd /var/www

chmod -R  777 *

everything just started working now.. the literary term "application folder" seems to mean /var/www
I was logged in using samba under the default admin (no password)
it kicked me out

now it shows pydio at the web interface

I tried to login with the admin but I just get "explode(): Empty delimiter" error in red at the bottom then it disapears.   alot happened in that update so maybe I give it a bit to do what ever it does in the background.. the dropdown that I am guessing would have samba or local  seems empty.  maybe it needs a reboot.

Proxmox has a fantastic WebUI so I don't remember the last time I launched via commandline. It also allows setting of root password at launch too. I just launched a fresh instance in PVE in the hope that the interface would tell me the command it used - earlier versions used to, but it seems not anymore... FWIW here is the conf file for the new container:

ONBOOT="no"

PHYSPAGES="0:1024M"
SWAPPAGES="0:1024M"
KMEMSIZE="465M:512M"
DCACHESIZE="232M:256M"
LOCKEDPAGES="512M"
PRIVVMPAGES="unlimited"
SHMPAGES="unlimited"
NUMPROC="unlimited"
VMGUARPAGES="0:unlimited"
OOMGUARPAGES="0:unlimited"
NUMTCPSOCK="unlimited"
NUMFLOCK="unlimited"
NUMPTY="unlimited"
NUMSIGINFO="unlimited"
TCPSNDBUF="unlimited"
TCPRCVBUF="unlimited"
OTHERSOCKBUF="unlimited"
DGRAMRCVBUF="unlimited"
NUMOTHERSOCK="unlimited"
NUMFILE="unlimited"
NUMIPTENT="unlimited"

# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="4G:4613734"
DISKINODES="800000:880000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair scheduler parameter
CPUUNITS="1000"
CPUS="1"
HOSTNAME="tkl-files.home.local"
SEARCHDOMAIN="home.local"
NAMESERVER="192.168.1.1 8.8.8.8"
IP_ADDRESS="192.168.1.123"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/123"
OSTEMPLATE="debian-7-turnkey-fileserver_13.0-1_amd64.tar.gz"

I'm sure that the root password is set via vzctl though. Once the container is created the first thing to do is start it (obviously). Then it will auto install all security updates from Debian repos. After that is finished then you need to run the inithooks as I mentioned. Once that is done then you are ready to go (either quit out of the Confconsole back to commandline, or just shut session).

TBH if I were you, I'd probably be inclined to start again... You should not need to do any tweaks or adjustments. If you do then there is something wrong with your setup... Make sure you wait for all the updates to install, then run through the inithooks before you do anything else...

TBH I'm not 100% clear on what you are referring to when you say the "web interface". Are you referring to Webmin (https via port 12321)? If so, you need to log in as 'root' (using the root password you set with vzctl i.e. the Linux root user credentials). If you mean Ajaxplorer (https/port 443) then that is 'admin' using the password you set with the inithook (from the commandline).

Once you have all that done, then you can create your new Linux users. You can use commandline or Webmin. Note: if you want the user to have access to the default share (/srv/storage) then add them to the 'sambashare' group. I just tested this via commandline:

adduser test
adduser test sambashare
smbpasswd -a test

If you use Webmin then you'll need to create the user and add the sambashare group (under System>>Users and Groups>>Create a new user) then add the Linux user as a Samba user (under Server>>Samba Windows File Sharing>>Convert Users).

Once I did that (the commandline version) I logged into the Ajaxplorer interface using the username 'test' and the password I set following the 'smbpasswd' command above.

Note that if you want to use other file transfer methods (e.g. FTP) with these same user accounts then you'll need to do further config (with the exception of root). SFTP (FTP over SSH) is installed by default but you'll need to add your users to the 'ssh' group if you want them to also use it. Also note that SFTP chroot jails are a bit tricky to implement and by default all SFTP users will have full read access to the whole filesystem. If you want a secure FTP with users being locked to their home dir (ie.e chroot jail) then I would suggest configuring FTPS (FTP over SSL/TLS) with a package such as ProFTPd or vsftpd.

But as I said, I use it on Proxmox and they were designed to be fairly tightly integrated into Proxmox from the get-go. AFAIK Proxmox uses a fairly recent RHEL6 (2.6.32) kernel (rebuilt to work with Debian).

When you first create your container from the template you will need to complete the 'first-boot' init scripts. They should auto start when you log in (as root: using the password you set when you launch the container). That will guide you through what needs to be done to get started. If for some reason they don't autostart (or you want to re-run them) you can do that with the 'turnkey-init' command.

Once that has been done it should just work...

Out of interest, what did you need to tweak to get it to work?