Skip to content
Docker image to build firmware for the Freifunk Magdeburg community.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Dockerfile
README.md

README.md

Freifunk Magdeburg Docker build image

Docker image to build firmware for the Freifunk Magdeburg community.

The build process is started automatically when the container is run. There is no need to manually run commands inside the container anymore.

Shell trail

This section shows the commands that are needed to run a build with the Docker image. Make sure you know what you are doing before hitting the Enter key.

Clone the repository:

git clone https://github.com/FreifunkMD/gluon-docker
cd gluon-docker/

Use the following commands on the host to create and run the docker image:

docker build -t ffmd-v2016.2.7 .
docker run -it --name ffmd ffmd-v2016.2.7

The container will automatically start the firmware build process.

The build process can be configured with build arguments:

docker build --build-arg FFMD_VERSION=tags/v0.38-beta.1 -t ffmd-v2016.2.7 .

To start the container with an arbitrary command, you can:

docker run -it --name ffmd ffmd-v2016.2.7 "/bin/bash"

You can run a shell in an existing container with the following command:

docker exec -it ffmd /bin/bash

To restart the image once it has been stopped:

docker start -i ffmd

Once you are done, container and image can be deleted by calling

docker rm ffmd
docker rmi ffmd-v2017.2.7

The build needs up to 60 GB of hard disk space. If the docker environment cannot provide the neccessary space, the paths /gluon/output and /gluon/openwrt/build_dir should be bound to a different directory:

docker run -it --name ffmd \
    -v "$(pwd)/firmwares:/gluon/output" \
    -v "$(pwd)/openwrt_build:/gluon/openwrt/build_dir" \
    ffmd-v2016.2.7

This will create and bind the directories firmware and openwrt_build in the current working directory to the container's output directories.

You can’t perform that action at this time.