COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20160305020959/https://docs.docker.com/opensource/ways/issues/

Products
- Pricing
- What is Docker?
Customers
Community
- Meetups
- Events
- Forums
- Community News
Partners
- Partner Programs
Company
Open Source
- Contribute

Quickstart containers Understand the architecture

Installation on Mac OS X Installation on Windows

Installation on Ubuntu Installation on Red Hat Enterprise Linux Installation on CentOS Installation on Fedora Installation on Debian Installation on Arch Linux Installation on CRUX Linux Installation on FrugalWare Installation on Gentoo Installation on Oracle Linux Installation on openSUSE and SUSE Linux Enterprise

Choose how to install Example: Manual install on cloud provider Example: Use Docker Machine to provision cloud hosts

Installation from binaries

Introduction

Hello world in a container Run a simple application Build your own images Network containers Manage data in containers Store images on Docker Hub

Best practices for writing Dockerfiles Create a base image Image management

Understand images, containers, and storage drivers Select a storage driver AUFS storage driver in practice Btrfs storage in practice Device mapper storage in practice OverlayFS storage in practice ZFS storage in practice

Docker container networking Work with network commands Get started with multi-host networking Configure container DNS in user-defined networks Default bridge network

Apply custom metadata

Automatically start containers Control and configure Docker with systemd PowerShell DSC Usage Process management with CFEngine Using Chef Using Puppet Using Supervisor with Docker Configuring and running Docker Runtime metrics Link via an ambassador container

Configuring Logging Drivers Amazon CloudWatch Logs logging driver Log tags for logging driver Fluentd logging driver Splunk logging driver journald logging driver

Run a local registry mirror

Docker security Protect the Docker daemon socket Using certificates for repository client verification

Content trust in Docker Automation with content trust Deploying Notary Manage keys for content trust Play in a content trust sandbox

AppArmor security profiles for Docker Seccomp security profiles for Docker

Access authorization plugin Extending Engine with plugins Docker network driver plugins Volume plugins Plugins API

Dockerizing MongoDB Dockerizing PostgreSQL Dockerizing a CouchDB service Dockerizing a Couchbase service Dockerizing a Node.js web app Dockerizing a Redis service Dockerizing a Riak service Dockerizing an SSH service Dockerizing an apt-cacher-ng service

Dockerfile reference Docker run reference

Use the Docker command line daemon attach build commit cp create diff events exec export history images import info inspect kill load login logout logs network connect network create network disconnect network inspect network ls network rm pause port ps pull push rename restart rm rmi run save search start stats stop tag top unpause update version volume create volume inspect volume ls volume rm wait

Remote API Remote API v1.22 Remote API v1.21 Remote API v1.20 Remote API v1.19 Remote API v1.18 Remote API v1.17 Remote API v1.16 Remote API v1.15 Remote API v1.14 Remote API client libraries docker.io accounts API

Migrate to Engine 1.10 Breaking changes Deprecated Engine Features FAQ

Swarm Overview How to get Swarm Evaluate Swarm in a sandbox Plan for Swarm in production Build a Swarm cluster for production

Learn the application architecture Deploy network infrastructure Setup cluster resources Deploy the application Troubleshoot the application

High availability in Swarm Swarm and container networks Discovery Provision with Machine

Filters Strategies

Overview Docker Swarm with TLS Configure Docker Swarm for TLS

create help join list manage swarm

Docker Swarm API

Overview of Docker Compose Install Compose Getting Started Using Compose with Swarm Quickstart: Compose and Django Quickstart: Compose and Rails Quickstart: Compose and WordPress Extending Services in Compose Networking in Compose Using Compose in Production Compose File Reference

Overview of docker-compose CLI CLI Environment Variables build config create down events help kill logs pause port ps pull restart rm run scale start stop unpause up

Command-line Completion Link Environment Variables Controlling startup order Frequently Asked Questions

Introducing Docker Hub Your Docker Hub account Teams & Organizations Repositories on Docker Hub Automated Builds Webhooks for automated builds Automated Builds with Bitbucket Automated Builds from GitHub Official Repositories on Docker Hub

Overview Trusted Registry

Install Docker Subscription for AWS (BYOL)) Install Docker Engine for AWS AMI (BDS) Install Trusted Registry for AWS AMI (BDS) Install on Microsoft Azure Install the Trusted Registry offline Manually Install the CS Docker Engine Manually install Trusted Registry Upgrade Trusted Registry and the CS Engine

Configuration overview Configure general settings Security configuration Storage configuration Auth configuration

Quick-start: Basic Workflow User guide Admin tasks Account and repository management Remove an image and garbage collection Trusted Registry License Support

Overview v1.3.3 API v1.4.0 API

Trusted Registry release notes Prior Trusted Registry release notes CS Engine release notes Prior CS Engine release notes

Release Notes

Introducing Docker Cloud Link to a Cloud Service Provider Link your Amazon Web Services account Link your DigitalOcean account Link your Microsoft Azure account Link your Packet account Link your SoftLayer account Set up self-hosted nodes Deploy your first node Deploy your first service

Learn about Dockerfiles and Docker Cloud Back up data volumes Create a proxy or load balancer Install the Deploy to Docker Cloud button Integrate with Slack Push images to Docker Cloud SSHing into a Docker Cloud-managed node Upgrade Docker Engine on a node Use the Docker Cloud Agent Using the Docker Cloud CLI

Introduction to deploying a Golang app Set up Prepare the app Push a Docker image to Docker Cloud's Registry Deploy the app as a Docker Cloud service Define environment variables Scale the service View logs Load-balance the service Provision a data backend for your service

Deploy a Python app Set up Python application Prepare the Python application Push an image to Docker Cloud's Registry Deploy the app as a Docker Cloud service Define environment variables Scale the service View logs Load-balance a Python service Provision a data backend for a Python service Data management with Volumes Python service stacks

Autodestroy Automated build Automated repository tests Automatic Container Restart Autoredeploy Deployment tags Manage service stacks Publish and expose service or container ports Redeploy running services Schedule a deployment Service API Roles Service discovery Spawn new containers Stack YAML reference Use triggers Work with data volumes

Known Issues in Docker Cloud Using Docker Cloud and Packet.net Using Docker Cloud on AWS

API reference

Machine Overview Install Machine Get started with a local VM Provision hosts in the cloud

Provision Digital Ocean Droplets Provision AWS EC2 Instances

Machine concepts and help Migrate from Boot2Docker to Machine

active config create env help inspect ip kill ls provision regenerate-certs restart rm scp ssh start status stop upgrade url

Driver options and operating system defaults Amazon Web Services Digital Ocean Generic Google Compute Engine IBM Softlayer Microsoft Azure Microsoft Hyper-V OpenStack Oracle VirtualBox Rackspace VMware Fusion VMware vCloud Air VMware vSphere exoscale

Command-line Completion

Docker Universal Control Plane Evaluation installation Plan a production installation Install UCP for production Upgrade UCP Deploy an application Integrate with Trusted Registry Set up container networking Set up high availability UCP Key/Value Store Backends

Monitor and troubleshoot UCP Manage and authorize users

dump-certs engine-discovery fingerprint help images install join uninstall upgrade

Get support Release Notes

Toolbox Overview

Kitematic User Guide: Intro & Overview Set up an Nginx web server Set up a Minecraft Server Creating a Local RethinkDB Database for Development Frequently Asked Questions Known Issues

Registry Overview Understanding the Registry Deploying a registry server Configuring a registry Working with notifications Recipes

HTTP API V2 Storage Drivers Token Authentication Implementation Token Authentication Specification

Getting help

Getting started with Notary Use the Notary client Understand the service architecture Running a Notary service

Server Configuration Signer Configuration Client Configuration Common Server and Signer Configurations

Notary Changelog

Quickstart contribution

README first Get the required software Set up for development on Windows Configure Git for contributing Work with a development container Run tests and test documentation

Understand how to contribute Find and claim an issue Work on your issue Create a pull request (PR) Participate in the PR review Advanced contributing Coding style checklist

Organize a Docker Meetup Organize our issues Support the community Testing contributions

Get started Find an issue Set up for Kitematic development Develop in Kitematic (work on an issue) Create a pull request (PR) Where to learn more

Docker Governance Advisory Board Board member profiles Code of conduct

FAQ for contributors Where to chat or get help Style guide for Docker documentation

Docker Release Notes Docker Glossary

Version 1.9 Version 1.8 Version 1.7 Version 1.6 Version 1.5 Version 1.4

Organize our issues

The Docker projects use GitHub issues to record issues and feature requests that come in from contributors. Help us organize our work by triaging. Triage is the process of reviewing incoming issue tickets, gathering more information about the issue, and verifying whether or not the issue is valid.

You should triage if you want to discover which Docker features other contributors think are important. Triage is a great choice if you have an interest or experience in software product management or project management.

What kind of issues can I triage?

Docker users and contributors create new issues if they want to:

report a problem they had with Docker software
request a new feature
ask a question

How do I triage?

Follow these steps:

Sign up for a Github account.
Visit a Docker repository and press the Watch button.

This tells GitHub to notify you of new issues. Depending on your settings, notification go to your GitHub or email inbox. Some of repositories you can watch are:

docker/docker	Docker the open-source application container engine
docker/machine	Software for the easy and quick creation of Docker hosts on your computer, on cloud providers, and inside your own data center.
kitematic/kitematic	Kitematic is a simple application for managing Docker containers on Mac OS X and Windows.
docker/swarm	Native clustering for Docker; manage several Docker hosts as a single, virtual host.
docker/compose	Define and run complex applications using one or many interlinked containers.

See the complete list of Docker repositories on GitHub.

Choose an issue from the list of untriaged issues.
Follow the the triage process to triage the issue.

The triage process asks you to add both a kind/ and a exp/ label to each issue. Because you are not a Docker maintainer, you add these through comments. Simply add a +label keyword to an issue comment:

Example

For example, the +exp/beginner and +kind/writing labels would triage an issue as beginner writing task. For descriptions of valid labels, see the the triage process

Triage another issue.

On this page: