v 0.2
6 Feb 13
The last few days, I've been playing with PC-BSD Jails via Warden. I've found that the BSD Jails work just great, as I've mentioned previously, however I've been having problems installing servers on a Debian Linux Jail. Some servers install without a hitch, and others just won't let the outside world see them.
A case in point is installing Citadel Groupware. In the Linux Jail, the two components can't talk to each other - Webcit, which provides the outward facing web interface, can't see the Citserver to talk on TCP 504. Installing on Virtualbox, no problems - it installs without a hitch.
Another example is the installation of Web Servers. Apache - nope. Nginx - worked out of the box. In all cases, the installation was using the standard Debian packages from the Main repository.
Debian Jail - Install Script
The way Debian is installed in a Linux Jail, is using the debootstrap command. The way this is set in the install script is simply:
debootstrap squeeze
However, there are several architectures for Debian, in particular, the ones we want use the FreeBSD kernel .. should we include the architecture we want? So, it would look like:
debootstrap --arch kfreebsd-i386 squeeze
or
debootstrap --arch kfreebsd-amd64 squeeze
I haven't really seen any difference, however I wonder ...
Citadel Again
Maybe I take a little longer for the concepts to sink in, but I've finally satisfied myself that the Debian packages do the same installation (albeit with files in different places - because it is Debian).
- The servers are installed
- The "citadel" user is created to run the server
- The init scripts are sorted.
How to re-configure the Citadel Server? There is a setup script in
"/usr/lib/citadel-server"
Run that script if you need to and you can adjust ports, and add an admin user.
Be aware, that Webcit ignores your setup instructions. Get a text editor and edit
"/etc/default/webcit"
to your liking.
Later .........
No comments:
Post a Comment