megasync_docker_arm(37) Language: English

Running Megasync on amhf using Docker

What is this?

Using the image presented here, you can synchronize files with Mega using a Docker container on an ARM device. Modifying the Dockerfile to build on top of debian:jessie instead of armhf/debian:jessie yields an image suitable for running on an AMD64 device.

Getting Started

Obtian the scripts from Github as follows

git clone

The image masysmalocal/megasync may then be built locally using make build. A Docker Hub automated build is not available due to exec format error if one attempts to automatically build this on Docker Hub.

You can run it as follows:

docker run --restart=always -d -p \
                        -v ...:/fs/backup \
                        -v ...:/home/linux-fan/.local/share/data \

Volumes are as follows:

Map the directory to be synced to this node.
Map a directory to contain the Megasync configuration to this one.

For successful read/write access from inside and outside the container, the files from the shared volumes should belong to user and group with ID 1024. If you want to use a different ID, change the Dockerfile accordingly and rebuild the image.

In order to graphically interact with the client, connect via VNC like this:

vncviewer localhost:0

About the Upgrader

An experimental package called mdvl-trival-automatic-update is supplied as part of this repository. It is installed inside the container as to keep a 24/7-running container up to date automatically. This script extends unattended-upgrades by a means of automatically chosing between multiple mirror hosts. By default, it checks for to be online and if that is not the case, it uses instead. This way, you can run your own local mirror to upgrade your server on a best-effort basis: If the upgrade happens while your local mirror is online, it will chose the local mirror. If the upgrade happens while the local mirror is not reachable, the process will take the upgrade from the internet.

If you wonder about supplying a .deb package as the source code – there is nothing more to it than the files contained so there is no need to provide a separate source code. If you want to rebuild the .deb, extract it's contents and use dpkg-deb or MDPC. If you use MDPC, the package belongs to the raw category and the files should be in a directory called after the package name.

Zum Seitenanfang