not a support question
l.manu
offlineMember
Hi,
Docker (https://www.docker.io/) is an open source application container engine.
Docker is only supported on 64-bit platforms.
I compiled kernel from configuration (config64) provided by SliTaz 5.
Also, I set CONFIG_NETFILTER_XT_MATCH_ADDRTYPE in kernel config (it is not set by default) and I have installed AUFS (AUFS support is optional but recommended).
Docker works fine.
docker.jpg (45.7 KB, 1,662 downloads) 10 years old 
alanyih
offlineAdministrator
Build, Ship and Run Any App, Anywhere
Docker - An open platform for distributed applications for developers and sysadmins.
alanyih
offlineAdministrator
By The Numbers - 2014.12.09
https://www.docker.com/company/aboutus/
16,000 GitHub stars
60 million Docker Engine downloads
40,000 "Dockerized" applications in the Docker Hub Registry
128 Docker Meetup Groups in 43 countries
700+ community contributors
40,000 third-party projects on GitHub using Docker as well as partnerships spanning PaaS, operating systems, hosting services, CI platforms, and more.
Over 50 user-generated case studies available from companies such as eBay, Rackspace, New Relic, Gilt, Spotify, Cloudflare, Yandex, Cambridge Healthcare, Yelp and RelatelQ.
docker-thanks.jpg (89.8 KB, 1,409 downloads) 10 years old docker-parters.jpg (72.4 KB, 2,833 downloads) 10 years old
alanyih
offlineAdministrator
Docker: Present and Future
http://www.infoq.com/articles/docker-future
Docker - the story so far
Docker is a toolset for Linux containers designed to ‘build, ship and run’ distributed applications. It was first released as an open source project by DotCloud in March 2013. The project quickly became popular, leading to DotCloud rebranded as Docker Inc (and ultimately selling off their original PaaS business). Docker 1.0 was released in June 2014, and the monthly release cadence that led up to the June release has been sustained since.
The 1.0 release marked the point where Docker Inc considered the platform sufficiently mature to be used in production (with the company and partners providing paid for support options). The monthly release of point updates shows that the project is still evolving quickly, adding new features, and addressing issues as they are found. The project has however successfully decoupled ‘ship’ from ‘run’, so images sourced from any version of Docker can be used with any other version (with both forward and backward compatibility), something that provides a stable foundation for Docker use despite rapid change.
The growth of Docker into one of the most popular open source projects could be perceived as hype, but there is a great deal of substance. Docker has attracted support from many brand names across the industry, including Amazon, Canonical, CenturyLink, Google, IBM, Microsoft, New Relic, Pivotal, Red Hat and VMware. This is making it almost ubiquitously available wherever Linux can be found. In addition to the big names many startups are growing up around Docker, or changing direction to be better aligned with Docker. Those partnerships (large and small) are helping to drive rapid evolution of the core project and its surrounding ecosystem.
A brief technical overview of Docker
....
alanyih
offlineAdministrator
slitaz-core64-check-config
slitaz-rolling-core64.iso 2014-10-27
root@slitaz:/home/tux# uname -a
Linux slitaz 3.2.53-slitaz64 #2 SMP Sun Oct 26 09:30:52 Europe 2014 x86_64 GNU/Linux
root@slitaz:/home/tux# check-config.sh
info: reading kernel config from /proc/config.gz ...
Generally Necessary:
- cgroup hierarchy: nonexistent??
(see https://github.com/tianon/cgroupfs-mount)
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_MACVLAN: enabled
- CONFIG_VETH: enabled
- CONFIG_BRIDGE: enabled
- CONFIG_NF_NAT_IPV4: missing
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: missing
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled
- CONFIG_NF_NAT: enabled
- CONFIG_NF_NAT_NEEDED: enabled
Optional Features:
- CONFIG_MEMCG_SWAP: missing
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_CGROUP_PERF: enabled
- Storage Drivers:
- "aufs":
- CONFIG_AUFS_FS: missing
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: missing
- "btrfs":
- CONFIG_BTRFS_FS: enabled
- "devicemapper":
- CONFIG_BLK_DEV_DM: enabled
- CONFIG_DM_THIN_PROVISIONING: missing
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: missing
slitaz-core64-check-config.png (62.3 KB, 1,837 downloads) 10 years old
alanyih
offlineAdministrator
Check runtime dependencies
https://docs.docker.com/installation/binaries
To run properly, docker needs the following software to be installed at runtime:
iptables version 1.4 or later
Git version 1.7 or later
procps (or similar provider of a "ps" executable)
XZ Utils 4.9 or later
a properly mounted cgroupfs hierarchy (having a single, all-encompassing "cgroup" mount point is not sufficient)Check kernel dependencies
Docker in daemon mode has specific kernel requirements. For details, check your distribution in Installation.
In general, a 3.8 Linux kernel is the minimum requirement for Docker, as some of the prior versions have known issues that are triggered by Docker. Linux kernel versions older than 3.8 are known to cause kernel panics and to break Docker.
The latest minor version (3.x.y) of the 3.10 (or a newer maintained version) Linux kernel is recommended. Keeping the kernel up to date with the latest minor version will ensure critical kernel bugs get fixed.
linux-namespaces-cgroup.jpg (124.5 KB, 1,530 downloads) 10 years old
alanyih
offlineAdministrator
In general, a 3.8 Linux kernel is the minimum requirement for Docker,
The latest minor version (3.x.y) of the 3.10 (or a newer maintained version) Linux kernel is recommended.
Linux namespaces & cgroups Availability:
Linux 3.8
http://kernelnewbies.org/Linux_3.8
Linux 3.8 was released on Mon, 18 Feb 2013.
This Linux release includes support in Ext4 for embedding very small files in the inode, which greatly improves the performance for these files and saves some disk space. There is also a new Btrfs feature that allows to replace quickly a disk, a new filesystem F2FS optimized for SSDs, support of filesystem mounts, UTS, IPC, PIDs, and network stack namespaces for unprivileged users, accounting of kernel memory in the memory resource controller, journal checksums in XFS, an improved NUMA policy redesign and, of course, the removal of support for 386 processors. Many small features and new drivers and fixes are also available.
- Prominent features in Linux 3.8
- Ext4 embeds very small files in the inode
- Btrfs fast device replacement
- F2FS, a SSD friendly file system
- User namespace support completed
- XFS log checksums
- Huge Pages support a zero page
- The memory resource controller supports accounting of kernel memory
- Automatic NUMA balancing
- Removal of support for 386 processors
- Driver and architecture-specific changes
- Various core changes
- Filesystems
- Block
- Crypto/keyring
- Security
- Perf
- Virtualization
- Networking
- Other news sites that track the changes of this release
alanyih
offlineAdministrator
The best way to understand Docker is to try it!
https://www.docker.com/tryit/
In this 10-minute tutorial, see how Docker works first-hand:
[..]
devl547
offline~ # cook my_life
>Docker (https://www.docker.io/) is an open source application container engine.
Just another "high scalability high availability enterprise production platform" bullshit?
alanyih
offlineAdministrator
boot2docker
http://boot2docker.io/
boot2docker is a lightweight Linux distribution based on Tiny Core Linux made specifically to run Docker containers. It runs completely from RAM, weighs ~27MB and boots in ~5s (YMMV).
See Frequently asked questions for more details.Features
- Kernel 3.16.7 with AUFS, Docker 1.3.2
- Container persistence via disk automount on /var/lib/docker
- SSH keys persistence via disk automount
- Host-only network for easy access to ports mapped by Docker
boot2docker.iso
https://github.com/boot2docker/boot2docker/releases/download/v1.3.2/boot2docker.iso
root@boot2docker:~# uname -a
Linux boot2docker 3.16.7-tinycore64 #1 SMP Thu Nov 20 00:06:13 UTC 2014 x86_64 GNU/Linux
root@boot2docker:~# dmesg | grep gcc
Linux version 3.16.7-tinycore64 (root@064f0e1ce709) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Thu Nov 20 00:06:13 UTC 2014
root@boot2docker:~# docker version
Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa
OS/Arch (client): linux/amd64
Server version: 1.3.2
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): 39fa2fa
root@boot2docker:~# docker info
Containers: 0
Images: 0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 0
Execution Driver: native-0.2
Kernel Version: 3.16.7-tinycore64
Operating System: Boot2Docker 1.3.2 (TCL 5.4); master : 495c19a - Mon Nov 24 20:40:58 UTC 2014
Debug mode (server): true
Debug mode (client): false
Fds: 10
Goroutines: 11
EventsListeners: 0
Init Path: /usr/local/bin/docker
root@boot2docker:~#
alanyih
offlineAdministrator
40,000 "Dockerized" applications in the Docker Hub Registry
1.
root@boot2docker:~# docker search slitaz
NAME DESCRIPTION STARS OFFICIAL AUTOMATED mastersrp/slitaz-core A 32bit version of the core SliTaz system ... 0
2.
root@boot2docker:~# docker pull mastersrp/slitaz-core
Pulling repository mastersrp/slitaz-core
3c2cb5d63685: Download complete
Status: Downloaded newer image for mastersrp/slitaz-core:latest
3.
root@boot2docker:~# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE mastersrp/slitaz-core latest 3c2cb5d63685 10 weeks ago 41 MB
4.
root@boot2docker:~# docker run mastersrp/slitaz-core ls -l
exec format error2014/12/3 21:47:19 Error response from daemon: Cannot start container f8042526bcb711ff76b27b3cd4288e11373b172e690e2742f6314b91ed7b2c21: exec format error
5.
root@boot2docker:~# docker run mastersrp/slitaz-core slitaz
exec format error2014/12/3 21:47:32 Error response from daemon: Cannot start container 01a8cfb9e3467cbfe7a8a6d9a95d7af7c9b836a194b3fa5482016c003fcb725e: exec format error
6.
root@boot2docker:~# docker run -i -t mastersrp/slitaz-core /bin/sh
exec format error2014/12/3 21:48:07 Error response from daemon: Cannot start container 7b35788dd3b729c33c1a316c51c9fff1e9cbef00b2950e4d6450f17d39b21dff: exec format error
root@boot2docker:~#
alanyih
offlineAdministrator
Linux kernel 3.16.7-slitaz
Linux boot2docker 3.16.7-tinycore64 #1 SMP Thu Nov 20 00:06:13 UTC 2014 x86_64 GNU/Linux
Linux version 3.16.7-tinycore64 (root@064f0e1ce709) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Thu Nov 20 00:06:13 UTC 2014
Kernel Version: 3.16.7-tinycore64
1. Linux kernel: patch aufs
2.
root@boot2docker:~# uname -a
Linux boot2docker 3.16.7-slitaz #1 SMP Mon Dec 1 11:18:28 UTC 2014 x86_64 GNU/Linux
root@boot2docker:~# dmesg | grep gcc
Linux version 3.16.7-slitaz (root@slitaz) (gcc version 4.6.3 (SliTaz) ) #1 SMP Mon Dec 1 11:18:28 UTC 2014
3.
root@boot2docker:~# docker version
Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa
OS/Arch (client): linux/amd64
Server version: 1.3.2
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): 39fa2fa
4.
root@boot2docker:~# docker info
Containers: 4
Images: 3
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 11
Execution Driver: native-0.2
Kernel Version: 3.16.7-slitaz
Operating System: Boot2Docker 1.3.2 (TCL 5.4); master : 495c19a - Mon Nov 24 20:40:58 UTC 2014
Debug mode (server): true
Debug mode (client): false
Fds: 11
Goroutines: 13
EventsListeners: 0
Init Path: /usr/local/bin/docker
5.
root@boot2docker:~# lsmod
Module Size Used by Not tainted
xt_addrtype 12288 2
xt_conntrack 12288 1
ipt_MASQUERADE 12288 1
iptable_nat 12288 1
nf_conntrack_ipv4 16384 2
nf_defrag_ipv4 12288 1 nf_conntrack_ipv4
nf_nat_ipv4 12288 1 iptable_nat
nf_nat 16384 3 ipt_MASQUERADE,iptable_nat,nf_nat_ipv4
nf_conntrack 57344 6 xt_conntrack,ipt_MASQUERADE,iptable_nat,nf_conntrack_ipv4,nf_nat_ipv4,nf_nat
bridge 61440 0
stp 12288 1 bridge
llc 12288 2 bridge,stp
ipv6 229376 13 bridge,[permanent]
cpufreq_conservative 12288 0
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
squashfs 28672 0
loop 20480 0
ppdev 12288 0
floppy 49152 0
parport_pc 24576 0
parport 28672 2 ppdev,parport_pc
intel_agp 12288 0
intel_gtt 16384 1 intel_agp
agpgart 28672 2 intel_agp,intel_gtt
pcspkr 12288 0
e1000 81920 0
i2c_piix4 12288 0
6.
root@boot2docker:~# modinfo nf_nat_ipv4
filename: kernel/net/ipv4/netfilter/nf_nat_ipv4.ko
license: GPL
alias: nf-nat-2
depends: nf_nat,nf_conntrack
vermagic: 3.16.7-slitaz SMP mod_unload
7.
root@boot2docker:~# zcat /proc/config.gz | grep AUFS
CONFIG_AUFS_FS=y
# CONFIG_AUFS_BRANCH_MAX_127 is not set
# CONFIG_AUFS_BRANCH_MAX_511 is not set
# CONFIG_AUFS_BRANCH_MAX_1023 is not set
CONFIG_AUFS_BRANCH_MAX_32767=y
CONFIG_AUFS_SBILIST=y
# CONFIG_AUFS_HNOTIFY is not set
# CONFIG_AUFS_EXPORT is not set
# CONFIG_AUFS_FHSM is not set
# CONFIG_AUFS_RDU is not set
# CONFIG_AUFS_SHWH is not set
# CONFIG_AUFS_BR_RAMFS is not set
CONFIG_AUFS_BR_HFSPLUS=y
CONFIG_AUFS_BDEV_LOOP=y
# CONFIG_AUFS_DEBUG is not set
root@boot2docker:~#
boot2docker-132.png (18 KB, 1,610 downloads) 10 years old kernel-xconfig-aufs.png (124.5 KB, 2,035 downloads) 10 years old
alanyih
offlineAdministrator
slitaz64-check-config
root@slitaz:~# uname -a
Linux slitaz 3.16.7-slitaz #1 SMP Mon Dec 1 11:18:28 UTC 2014 x86_64 GNU/Linux
root@slitaz:~# ./check-config.sh
info: reading kernel config from /proc/config.gz ...
Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_MACVLAN: enabled
- CONFIG_VETH: enabled
- CONFIG_BRIDGE: enabled
- CONFIG_NF_NAT_IPV4: enabled
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled
- CONFIG_NF_NAT: enabled
- CONFIG_NF_NAT_NEEDED: enabled
Optional Features:
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_RESOURCE_COUNTERS: enabled
- CONFIG_CGROUP_PERF: enabled
- Storage Drivers:
- "aufs":
- CONFIG_AUFS_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- "btrfs":
- CONFIG_BTRFS_FS: enabled
- "devicemapper":
- CONFIG_BLK_DEV_DM: enabled
- CONFIG_DM_THIN_PROVISIONING: enabled
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
slitaz64-check-config.png (46.6 KB, 1,487 downloads) 10 years old You must log in to post.
