2017-04-14

6 billion pulls from Docker Hub, another billion every 6 weeks



6 billion pulls from Docker Hub,
another billion every 6 weeks
@solomonstre #LinuxCon


1 billion=1,000,000,000

1. Docker Hub Reaches Over 1.2 Billion Pulls
https://blog.docker.com/2015/11/docker-hub-billion-pulls/



2. Docker Community Passes Two Billion Pulls!
https://blog.docker.com/2016/02/docker-hub-two-billion-pulls/



3. 6 billion pulls from Docker Hub,
another billion every 6 weeks
@solomonstre #LinuxCon

https://twitter.com/docker/status/783226960172515328
https://blog.docker.com/2016/10/introducing-infrakit-an-open-source-toolkit-for-declarative-infrastructure/


It started in 2014 with libcontainer and libnetwork. In 2015 we created runC and co-founded OCI with an industry-wide set of partners to provide a standard for container runtimes, a reference implementation based on libcontainer, and notary, which provides the basis for Docker Content Trust. From there we added containerd, a daemon to control runC, built for performance and density. Docker Engine was refactored so that Docker 1.11 is built on top of containerd and runC, providing benefits such as the ability to upgrade Docker Engine without restarting containers. In May 2016 at OSCON, we open sourced HyperKit, VPNKit and DataKit, the underlying components that enable us  to deeply integrate Docker for Mac and Windows with the native Operating System. Most recently,  in June, we unveiled SwarmKit, a toolkit for scheduling tasks and the basis for swarm mode, the built-in orchestration feature in Docker 1.12.

4. As of March 1, 2017, we crossed 11 billion pulls from the public registry!
https://blog.docker.com/2017/04/enterprise-ready-software-docker-store/

2017-03-28

Slitaz64 -- Endpoint


Endpoint
Endpoint https://tiny-bartik-1436.arukascloud.io/packages/

What is Endpoint
https://arukas.io/en/help-en/endpoint-en/
Instance IP Address is dynamic IP address.
When an instance needs to be rebooted for some reasons, its port are change. Can not always use the same port.

but, Endpoint URL is always the same.
Always-on connection it is supposed to be through the Endpoint.

Endpoint URL is mapped to the first port only.
ex:
port#1: 3456 <= mapped to Endpoint
port#2: 80
port#3: 443
Endpoint need all port opened after endpoint enabled.

EndPoint URL is HTTP backend support. (TCP/UDP not suppoted.)
This is intended to be used in a web server and API Server.

Entity of Endpoint is a load balancer. This will load balance the communication of multiple back-end instance automatically.

All of the instances automatically get rebooted almost every week, The average life span of the ip address and port is one week. Sometimes it changes in one day.

Slitaz64 -- mirror1 : ARUKAS CLOUD



mirror1 : ARUKAS CLOUD

Endpoint https://tiny-bartik-1436.arukascloud.io/packages/


tux@slitaz:~$ wget --check-certificate=quiet https://tiny-bartik-1436.arukasclod.io/packages/packages.md5
--2017-03-18 22:53:26-- https://tiny-bartik-1436.arukascloud.io/packages/packages.md5
Resolving tiny-bartik-1436.arukascloud.io (tiny-bartik-1436.arukascloud.io)... 153.125.239.164
Connecting to tiny-bartik-1436.arukascloud.io (tiny-bartik-1436.arukascloud.io)|153.125.239.164|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 80014 (78K) [application/octet-stream]
Saving to: ‘packages.md5’
packages.md5 100%[===================>] 78.14K --.-KB/s in 0.1s
2017-03-18 22:53:27 (603 KB/s) - ‘packages.md5’ saved [80014/80014]

tux@slitaz:~$ tail -5 packages.md5
8959db35ba02b994c0573e553657b0bc yasm-dev-1.3.0-x86_64.tazpkg
a19b9e7f9eabb359559df66061957929 ytree-1.97-x86_64.tazpkg
1bb1b80f76b9a367158da0c930ef6b23 zip-3.0-x86_64.tazpkg
36dddd22f16e742f9b8c5570170d534c zlib-1.2.8-x86_64.tazpkg
cfc5eef6981df97da057710d3cb7a199 zlib-dev-1.2.8-x86_64.tazpkg

tux@slitaz:~$ cat packages.md5 | wc -l
1212
tux@slitaz:~$


2017-03-14

Slitaz64 -- SliTaz Web Server

SliTaz Web Server


 
docker pull slitaz/slitaz-lighttpd
https://hub.docker.com/r/slitaz/slitaz-lighttpd/
http://doc.slitaz.org/en:handbook:webserver

tux@slitaz:~$ docker run -d -P slitaz/slitaz-lighttpd
Unable to find image 'slitaz/slitaz-lighttpd:latest' locally
latest: Pulling from slitaz/slitaz-lighttpd

986f76552751: Pull complete
443082f2095a: Pull complete
2a39471c7bf0: Pull complete
Digest: sha256:ebf93fa93f15acb18b0b1d74f88d416fd3a1c181bdecc7ab266b9c9102b1c42d
Status: Downloaded newer image for slitaz/slitaz-lighttpd:latest
81b7262138595b2f066f337aab3c865d9dfe5710a7b32e6f2f3aa05e55512c03

tux@slitaz:~$ docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                   NAMES
81b726213859        slitaz/slitaz-lighttpd   "lighttpd -D -f /etc/"   8 minutes ago       Up 8 minutes        0.0.0.0:32769->80/tcp   small_sinoussi

tux@slitaz:~$ ps | grep proxy
 2504 root       0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 32769 -container-ip 172.17.0.2 -container-port 80
tux@slitaz:~$