| Hosting provider uses OpenVZ - what are the minimum container support requirements? [message #51566] |
Wed, 30 July 2014 04:50  |
adfhogan
Messages: 3
Registered: July 2014
Location: Melbourne, Australia
|
Junior Member |
|
|
Hi folks,
Recently I've decided to try and move from an aging dedicated hosting system at one provider, to an OpenVZ solution at another provider. Out of the distribution choices (CentOS, Debian, Ubuntu, Fedora), I chose Debian as I prefer apt based systems over RPM (what I'm used to).
Anyway, on the existing host, I've been using Debian 'testing' aka 'Jessie'. On the OpenVZ container I have, they provide Debian 'stable' aka 'wheezy' as the most modern release.
Upon realising that it was container based virtualisation, I knew not to touch the kernel version (and indeed figured that it wouldn't be using usual boot manager, and that indeed there probably wasn't a boot sector as such as they're using simfs), but then attempted to install newer Apache (2.4) and some related packages via some apt version pinning trickery. I successfully got the packages installed, but when I went to reboot the container, I found that something had been erased by the upgrades (I'm thinking maaaaaybe it was related to init/systemd/sysvinit but that's me taking a wild guess based upon some error messages I saw mentioning init).
When I spoke with the hosting company, they indicated to get the VM at least functional so I could get files off it, that some things had been erased in /dev/, /etc/ and /lib/, that they'd loaded some dependencies back in, but things were still not functioning as they should. They've reset my hosting now so it's "factory fresh", but I obviously don't want to hose the support components like I did last time.
Is there a guide as to which support components are required in an OpenVZ container, so I can try my best to either maintain them or upgrade them safely to compatible systems?
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
