lu1as/aptly repository overview

⁠docker-aptly

docker image for aptly⁠ debian repository management

Docker hub: hub.docker.com/r/lu1as/aptly⁠

⁠How to start

On start the entrypoint script will create a gpg key for package signing. You can skip this by setting GPG_BOOTSTRAP to false, e.g. if you want to use an existing gpg key. Moreover a repository with packages located in /incoming will be created and published. This step is also skippable by setting REPO_BOOTSTRAP to false. If /incoming doesn't contain any packages, the script will fail. REPO_AUTO_IMPORT enables a cronjob, which checks /incoming every 30 minutes for updates.

The volume mounted at /aptly has to be owned by uid 1000 and gid 1000. Otherwise the container user aptly won't have write permissions.

Example with automated repository creation:

docker run -v some-packages:/incoming \
    -v aptly-data:/aptly \
    -v /dev/urandom:/dev/random \ # required with boot2docker for gpg key generation
    -e GPG_NAME=aptly-admin \
    -e [email protected] \
    -e GPG_PASSPHRASE=secret \
    -p 8080:8080 lu1as/aptly

Example with manual repository creation:

docker run -it -v aptly-data:/aptly \
    -v /dev/urandom:/dev/random \ # required with boot2docker for gpg key generation
    -e REPO_BOOTSTRAP=false \
    -e GPG_BOOTSTRAP=false \
    -p 8080:8080 lu1as/aptly bash

checkout www.aptly.info/doc⁠ for following steps