docker-aptly

docker-aptly is container with aptly backed by nginx.

aptly is a swiss army knife for Debian repository management: it allows you to mirror remote repositories, manage local package repositories, take snapshots, pull new versions of packages along with dependencies, publish as Debian repository. More info are on aptly.info and on github.

nginx is an HTTP and reverse proxy server, a mail proxy server, and a generic TCP proxy server, originally written by Igor Sysoev. More info is on nginx.org.

It project use supervisor to manage multiple processes in the container. It configured to start nginx & aptly api server.

Quickstart

Create docker aptly-data volume if it doesn't exist, otherwise use directory:
```
docker volume create --name aptly-data
```
Also you can use --driver option. By default it equals to local. More info is here.

All of aptly's data (including PGP key and GPG keyrings) is bind mounted outside of the container to preserve it if the container is removed or rebuilt.
If you want to customize image or build the container locally, check out this repository and build, otherwise skip this step and use prepared image from DockerHub:
```
git clone https://github.com/ludwig/docker-aptly.git
docker build docker-aptly --tag ludwig/aptly:latest
```
If you decide build own I suggest use docker-compose commands. It will build own image before use.
Then generate keypair. It won't regenerate that, if you already have keypair:
```
docker run --rm --log-driver=none \
  --env FULL_NAME="First Last" \
  --env EMAIL_ADDRESS="your@email.com" \
  --env GPG_PASSPHRASE="PickAPassword" \
  --volume aptly-data:/opt/aptly \
  ludwig/aptly:latest /opt/gen_keys.sh
```
FULL_NAME and EMAIL_ADDRESS will be associated with the GPG apt signing key.

Keep in the mind that the GPG passphrase which you specified in GPG_PASSPHRASE using ONLY BY USERS (at the external container) for:
1. Generating GPG keys (In the temporary container)
2. Singing Aptly packages (using CLI tool or REST API)
Keep your GPG passphrase separately from the GPG key pair.

Run aptly and nginx

docker run \
  --detach=true \
  --log-driver=syslog \
  --restart=always \
  --name="aptly" \
  --publish 80:80 \
  --volume aptly-data:/opt/aptly \
  ludwig/aptly:latest

If it returned (usualy on macOS):

docker: Error response from daemon: failed to initialize logging driver: Unix syslog delivery error.

Probably you haven't some driver. Execute docker rm aptly and try again without --log-driver=syslog.

Flag	Explanation
`--detach=true`	Run the container in the background
`--log-driver=syslog`	Send nginx logs to syslog on the Docker host (requires Docker 1.6 or higher), more info is here.
`--restart=always`	Automatically start the container when the Docker daemon starts
`--name="aptly"`	Name of the container
`--volume aptly-data:/opt/aptly`	Path (if you want set path use absolute path) or volume's name that aptly will use to store his data : mapped path in the container
`--publish 80:80`	Docker host port : mapped port in the container

Next steps
- You can manage docker container with docker or docker-compose. For example:
```
docker start aptly
docker restart aptly
docker stop aptly
docker rm aptly
```
- Use docker volume to manage created volume.
- Configure your own debian-repository. See here.
  
  You can also use Aptly REST API at YOUR-HOST/api. You need to generate htpasswd file before.
```
docker run --rm --log-driver=none \
--env USER="admin" \
--env PASS="passwd" \
--volume aptly-data:/opt/aptly \
ludwig/aptly:latest /opt/gen_htpasswd.sh
```
  After executing:
```
curl -u admin:passwd http://YOUR-HOST/api/version
```
  Security: Please note using http is not safety (your password sends as plain text). Add mandatory SSL encryption for /api via proxy server fe nginx. See here.
- Configure clients. See here.

Manage locally

If you want to build and run locally I suggest use docker-compose. But before create volume and generate keypair.

By default, Docker will map port 80 on the Docker host to port 80 within the container where nginx is configured to listen. You can change the external listening port to map to any port you like. Change the docker-compose file if you use him.

git clone https://github.com/ludwig/docker-aptly
cd docker-aptly/

# Build and run
# `--build` - if rebuild is requiring
# `-d` - run container in the background
# More info at: `docker-compose up --help`
docker-compose up -d --build

# Stop & remove (it doesn't remove created volumes)
docker-compose down

# Start / restart / stop container
docker-compose start
docker-compose restart
docker-compose stop

Troubleshooting w same container name

May be conflict if you already pull aptly from docker hub:

ERROR: for aptly Cannot create container for service aptly: Conflict. The container name "/aptly" is already in use by container "85de5904f6fc73c04f4f8e7d08a09a1a63c2ba28afb5ce45aa9578ebdefeadc7". You have to remove (or rename) that container to be able to reuse that name.

In this situation you need remove currently aptly container (or rename it):

docker rm 85de5904f6fc73c04f4f8e7d08a09a1a63c2ba28afb5ce45aa9578ebdefeadc7

Setup a client for use your repo

Fetch the public PGP key from your aptly repository and add it to your trusted repositories
```
wget http://YOUR_HOST_FOR_APTLY/aptly_repo_signing.key
apt-key add aptly_repo_signing.key
```

Backup then replace /etc/apt/sources.list

cp /etc/apt/sources.list /etc/apt/sources.list.bak
echo "deb http://YOUR_HOST_FOR_APTLY/ ubuntu main" > /etc/apt/sources.list
apt-get update

ubuntu & main may be another. It's require from your repos on aptly.

Configure the repository

Copy files to volume. Fist of all start docker container, because access to volume produced through him. Copy files to container (volume) directory, use docker cp:
```
docker cp aptly:/opt/aptly/<SRC_PATH> <DEST_PATH>
docker cp <SRC_PATH> aptly:/opt/aptly/<DEST_PATH>
```

Create and update debian-repo:

# Attach container
docker exec -it aptly /bin/bash

# Create repository folder
aptly repo create -comment="ROS packages for Raspbian Stretch" -component="main" -distribution="stretch" rpi-ros-kinetic

# Add deb-packages to index from `/opt/aptly/ros-kinetic-*`
aptly repo add rpi-ros-kinetic /opt/aptly/ros-kinetic-*

# Publish updates
aptly publish repo rpi-ros-kinetic rpi-ros-kinetic

Add new packages:

# Add deb-packages to index from `/opt/aptly/ros-kinetic/`
aptly repo add rpi-ros-kinetic /opt/aptly/ros-kinetic/

# Publish updates
aptly publish update stretch rpi-ros-kinetic

Read the official documentation for learn more about aptly.

Create a mirror of Ubuntu's main repository

Attach to the container. How attach? See here.
Run /opt/update_mirror_ubuntu.sh.

By default, this script will automate the creation of an Ubuntu 14.04 Trusty repository with the main and universe components, you can adjust the variables in the script to suit your needs.

If the script fails due to network disconnects etc, just re-run it.

The initial download of the repository may take quite some time depending on your bandwidth limits, it may be in your best interest to open a screen, tmux or byobu session before proceeding.

For host a mirror of Ubuntu's main repository, you'll need upwards of 80GB+ (x86_64 only) of free space as of Feb 2016, plan for growth.

When the script completes, you should have a functional mirror that you can point a client to.

For create Debian's mirror use /opt/update_mirror_debian.sh.

Licensed under the Apache License, Version 2.0