plone

docker-registry-0.9.1-1.lbn19.noarch
Registry server for Docker (hosting/delivering of repositories and images).
Located in LBN / … / Core Linux / BastionLinux 19
docker-registry-0.9.1-1.lbn19.noarch
Registry server for Docker (hosting/delivering of repositories and images).
Located in LBN / … / Cloud Computing / BastionLinux 19
docker-selinux-1.12.1-13.git9a3752d.fc25.x86_64
SELinux policy modules for use with Docker.
Located in LBN / … / Core Linux / BastionLinux 25
docker-selinux-1.12.1-6.gitf1040da.lbn19.x86_64
SELinux policy modules for use with Docker.
Located in LBN / … / Core Linux / BastionLinux 19
docker-selinux-1.12.1-6.gitf1040da.lbn19.x86_64
SELinux policy modules for use with Docker.
Located in LBN / … / Cloud Computing / BastionLinux 19
docker-swarm-0.4.0-1.lbn19.x86_64
Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Flynn, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself. Like other Docker projects, Swarm follows the "batteries included but removable" principle. It ships with a set of simple scheduling backends out of the box, and as initial development settles, an API will be developed to enable pluggable backends. The goal is to provide a smooth out-of-the-box experience for simple use cases, and allow swapping in more powerful backends, like Mesos, for large scale production deployments.
Located in LBN / … / Cloud Computing / BastionLinux 19
docker-utils-1.9.0-5.git11b81f9.lbn19.x86_64
External utilities for the docker experience
Located in LBN / … / Cloud Computing / BastionLinux 19
docker-utils-1.11.1-2.gitaaa9488.lbn19.x86_64
External utilities for the docker experience
Located in LBN / … / Core Linux / BastionLinux 19
docker-v1.10-migrator-1.10.3-3.gitd93ee51.lbn19.x86_64
Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
Located in LBN / … / Cloud Computing / BastionLinux 19
docker-v1.10-migrator-1.12.6-6.gitae7d637.fc25.x86_64
Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
Located in LBN / … / Cloud Computing / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 452 453 454 455 456 457 458 ... 4868

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.