- Arch Linux
For a while I have been running OwnCloud to share images. I use a Raspberry Pi with Arch Linux and run OwnCloud through Docker.
In conclusion, the setup is not too difficult, accessing the Cloud through dedicated clients are reasonably fast, but the web interface is quite slow.
To make more room for storage I have chosen the small GNU/Linux Distribution Arch Linux as the operating system.
I am new to Arch Linux and for future reference I include a section about installing and setting up.
Installation instructions for Raspberry Pi can be found here.
On a fresh system
root is the only user and has username
The first thing to do is to change the password of
Bring the package manager Pacman and system up to date with
A few necessary packages for me are
To be able run
base-devel is also needed.
When running a “cloud”, I find it useful to be able to monitor network traffic.
nload fits my needs and taste.
To search for the package
pacman -Ss <package>.
To generate the
locate database run
Add a new user, set information and add a password:
Add the user to the
- Copy the line starting with
Change the shell to zsh with
chsh -s zsh.
OwnCloud has a bunch of dependencies and to cut that corner I run OwnCloud in a Docker container.
Installing and running Docker is explained at Docker’s webpage.
Remember to add user to
One problem with using Docker on a Raspberry Pi is that the Pi is a 32 bit computer and most containers need a 64 bit computer. At the time of writing I have only found one container that works with a Pi and it is not the latest version of OwnCloud.
Download the container and start it with connections for HTTP(S):
The Docker package can be updated while the container is running, but the Docker client does not communicate with a container started under a previous version. Hence, from time to time it may be neccessary to stop and start a container.
At some point Docker began to complain when I restarted a stopped container (the error message is forgotten). Eventually I got it working by starting Docker with
One unfortunate thing is that despite the request, the docker process is not daemonized; I execute the command in a tmux session.
With Docker running again, the container can be started with
docker start CONTAINER ID, where
CONTAINER ID is found from
docker ps -a.
OwnCloud problems (2016-04-10)
My setup is working fine, but at some point my OwnCloud user ran out of space (as set in OwnCloud) and OwnCloud did not fail gracefully. In fact, I experienced a complete meltdown of OwnCloud – I could not access it in any way and eventually I deleted and reinstalled the container. Unfortunately this also meant that my OwnCloud settings and in particular the users and their passwords were lost.