Installing Node.js + Ghost in an Ubuntu 14.04 LXC Container
I had to set up a blog for an interaction design course that I am taking this semester. I figured this would be the perfect opportunity to play with Node.js and work with the absolutely beautiful Ghost blogging platform. I installed all of this on my primary Linode server that hosts this blog among other things. I like to keep my server neat, so whenever I am working with a new technology that I have not used before, especially when I know it is going to install a bunch of random files and run a bunch of random scripts that I will never be able to track down, I like to put it all into an LXC Container. Aside from a few snags, the installation was pretty straightforward. I followed theinstallation guide on the Ghost github site and had to make a couple small changes due to this issue. The interesting part of this was getting the container to be accessible from the outside world. I used apache’s mod_proxy module to forward requests to the new subdomain that I created directly to Ghost which was running in my LXC container. I have seen a couple different approaches to making containers accessible to the outside world but I think that this approach works well especially if you are hosting multiple sites on the same server.
Installing Your Container
I suppose this part is optional, you can just as well run this in a regular server or VM. However, if you like to put things into tiny little boxes like me, read on! The following should be run as root.apt-get install lxclxc-create -t download -n nodejs
During the template selection choose ubuntu, trusty, and amd64
Start the Container as a Daemon
lxc-start -n nodejs -d
Open a screen session to attach the container.
Why? Because “If it’s worth doing, it’s worth doing in screen”
screen -dRR node
lxc-attach -n nodejs
Installing Node.js and Ghost
Now that we have our shiny new container, lets get Node.js and Ghost installed. Since containers come with a very minimal set of software, we will install some additional utilities as well. The following should be run as root inside of your container. The only change I had to make from the official install guide was installing nodejs-legacy along with all the other stuff. Take a look at the issue linked to above if you are interested in more information.apt-get install wget unzip nodejs npm nodejs-legacyCreate a Directory for your Ghost blog and go into it
mkdir ghost cd ghost
Download and Unzip Ghost
wget https://ghost.org/zip/ghost-0.5.8.zip
unzip ghost-0.5.8.zipInstall Ghost
npm install –production
Since we are in a container, in order to be able to access ghost from the host
machine we will need to edit the config.js file and change the values of 127.0.0.1 to 0.0.0.0.
vim config.js
:%s/127.0.0.0.1/0.0.0.0/gStart Ghost
npm start
root@hci:/ghost#npm start
> ghost@0.5.8 start /ghost > node index Migrations: Up to date at version 003 Ghost is running in development… Listening on 0.0.0.0:2368 Url configured as: http://localhost:2368 Ctrl+C to shut down
Apache Proxy to Container
The last step of this is to set up the Virtual Host config file to proxy requests to our new Node.js container.# Grab the IP address of your container lxc-ls --fancyLoad the appropriate apache proxy modules
a2enmod proxy
a2enmod proxy_httpConfigure the Virtual Host file to set up the proxy it should look something like this. Be sure to replace the IP address listed below with the IP address of your actual container.
<VirtualHost *:80>
Admin email, Server Name (domain name), and any aliases
ServerAdmin [email protected]
ServerName hci.levlaz.orgProxyVia full
ProxyPreserveHost on<proxy>
Order deny,allow
Allow from all</proxy>
ProxyPass / https://10.0.3.101:2368/
ProxyPassReverse / https://10.0.3.101:2368/</Virtualhost>
Restart apache to clean things up
service apache2 restart
Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.
Check out some more stuff to read down below.
Most popular posts this month
Recent Favorite Blog Posts
This is a collection of the last 8 posts that I bookmarked.
- Deeper dive: Were Touch Bar’s problems software rather than hardware? from Unsung
- Joining Cursor from Fatih Arslan
- Pluralistic: Digital sewer socialism (08 Aug 2026) from Pluralistic: Daily links from Cory Doctorow
- Pluralistic: Enshittification and Reverse Centaurs go global (29 Jul 2026) from Pluralistic: Daily links from Cory Doctorow
- AI Mania Is Eviscerating Global Decision-Making from Ludicity
- The default person from https://popagandhi.com/
- No-One Escapes the Permanent Underclass from Fernando Borretti
- Is it ethical to use AI? from charity.wtf
Articles from blogs I follow around the net
An Ode to Links
A URL is a technical thing: a hostname, a path, a port, an origin, some query parameters, etc. But a link is a cultural thing: an invitation, a citation, a gift, a shortcut, a connection. All from a simple idea: here’s a thing that points to another thing,...
via Jim Nielsen’s Blog September 10, 2026I don't like it but the Trump DoJ is right on AI and fair use
I've written about this topic a number of times before, but in this case I'm tempted to re-use the popular meme "When the worst person in the world makes a good point," as I did awhile back when I wrote about Elon Musk&
via The Torment Nexus September 10, 2026“A great look at the destructive power of an uncaught Infinity value”
There are two distinct flavors of speedrunning: completing a game as fast as possible through feats of extraordinary mastery, timing, and precision, completing a game as fast as possible by finding all sorts of bugs and exploits in the game (commonly known...
via Unsung September 10, 2026Generated by openring