1 |
On Tue, 24 Oct 2017 07:35:35 -0400 |
2 |
Todd Goodman <tsg@×××××××××.net> wrote: |
3 |
|
4 |
> On 10/23/2017 10:46 PM, tuxic@××××××.de wrote: |
5 |
> > |
6 |
> >>>> Hi Robert, |
7 |
> >>>> |
8 |
> >>>> oh YEAH! |
9 |
> >>>> Thanks a lot for that quick start! |
10 |
> >>>> |
11 |
> >>>> I didi it, but... |
12 |
> >>>> #>eix -I docker |
13 |
> >>>> [I] app-emulation/docker |
14 |
> >>>> Available versions: 17.03.2^si (~)17.06.2^si (~)17.09.0^si |
15 |
> >>>> **9999^si {apparmor aufs btrfs +container-init +device-mapper |
16 |
> >>>> hardened overlay pkcs11 seccomp} Installed versions: |
17 |
> >>>> 17.09.0^si(05:48:14 PM 10/23/2017)(container-init device-mapper |
18 |
> >>>> seccomp -apparmor -aufs -btrfs -hardened -overlay -pkcs11) |
19 |
> >>>> Homepage: https://dockerproject.org |
20 |
> >>>> Description: The core functions you need to create |
21 |
> >>>> Docker images and run Docker containers |
22 |
> >>>> |
23 |
> >>>> [I] app-emulation/docker-proxy |
24 |
> >>>> Available versions: 0.8.0_p20161111 (~)0.8.0_p20170917^t |
25 |
> >>>> **9999 Installed versions: 0.8.0_p20170917^t(05:46:10 PM |
26 |
> >>>> 10/23/2017) Homepage: |
27 |
> >>>> https://github.com/docker/libnetwork Description: Docker |
28 |
> >>>> container networking |
29 |
> >>>> |
30 |
> >>>> [I] app-emulation/docker-runc |
31 |
> >>>> Available versions: 1.0.0_rc2_p20170308^t |
32 |
> >>>> (~)1.0.0_rc3_p20170706^t (~)1.0.0_rc4_p20170917^t {+ambient |
33 |
> >>>> apparmor hardened +seccomp} Installed versions: |
34 |
> >>>> 1.0.0_rc4_p20170917^t(05:46:07 PM 10/23/2017)(ambient seccomp |
35 |
> >>>> -apparmor -hardened) Homepage: http://runc.io |
36 |
> >>>> Description: runc container cli tools (docker fork) |
37 |
> >>>> |
38 |
> >>>> |
39 |
> >>>> #>groups |
40 |
> >>>> wheel mail uucp audio cdrom video games cdrw usb users docker |
41 |
> >>>> wireshark vboxusers vlock realtime ^----^ |
42 |
> >>>> |
43 |
> >>>> (as root) |
44 |
> >>>> #>/etc/init.d/docker start |
45 |
> >>>> * WARNING: docker has already been started |
46 |
> >>>> (so it is runnig) |
47 |
> >>>> |
48 |
> >>>> (as user again) |
49 |
> >>>> #>docker run --name firefox -e DISPLAY=$DISPLAY |
50 |
> >>>> --device /dev/snd -v /tmp/.X11-unix:/tmp/.X11-unix -v |
51 |
> >>>> $XAUTHORITY:/tmp/.host_Xauthority:ro -dti openhs/firefox-ubuntu |
52 |
> >>>> docker: Cannot connect to the Docker daemon at |
53 |
> >>>> unix:///var/run/docker.sock. Is the docker daemon running?. See |
54 |
> >>>> 'docker run --help'. [1] 10401 exit 125 docker run --name |
55 |
> >>>> firefox -e DISPLAY=$DISPLAY --device /dev/snd -v -v -dti |
56 |
> >>>> |
57 |
> >>>> Hmmmm...seems I missed something... |
58 |
> >>>> |
59 |
> >>>> Cheers |
60 |
> >>>> Meino |
61 |
> >>>> |
62 |
> >>>> |
63 |
> >>>> |
64 |
> >>>> |
65 |
> >>> Found this in dmesg |
66 |
> >>> |
67 |
> >>> [ 1587.391861] device-mapper: table: 254:0: thin-pool: unknown |
68 |
> >>> target type [ 1587.391863] device-mapper: ioctl: error adding |
69 |
> >>> target to table |
70 |
> >>> |
71 |
> >>> these two lines are added when I try to start /etc/ini.d/docker |
72 |
> >>> as root. |
73 |
> >>> |
74 |
> >>> Cheers |
75 |
> >>> Meino |
76 |
> >>> |
77 |
> >>> |
78 |
> >>> |
79 |
> >> I could this problem by defining |
80 |
> >> |
81 |
> >> CONFIG_DM_THIN_PROVISIONING=y |
82 |
> >> |
83 |
> >> in the kernel, recompile it and the message disappears. |
84 |
> >> BUT: |
85 |
> >> still docker does not start... |
86 |
> >> |
87 |
> >> How can I fix that? |
88 |
> >> |
89 |
> >> Cheers |
90 |
> >> Meino |
91 |
> >> |
92 |
> >> |
93 |
> > Next fix: |
94 |
> > Need to activate the complete cgroup features. |
95 |
> > |
96 |
> > Now I get this error message in /var/log/docker.log |
97 |
> > |
98 |
> > time="2017-10-24T04:42:39.358339658+02:00" level=info msg="Loading |
99 |
> > containers: start." time="2017-10-24T04:42:39.869600530+02:00" |
100 |
> > level=error msg="could not get initial namespace: no such file or |
101 |
> > directory" time="2017-10-24T04:42:39.884438663+02:00" level=error |
102 |
> > msg="failed to set to initial namespace, |
103 |
> > readlink /proc/4588/task/4588/ns/net: no such file or directory, |
104 |
> > initns fd -1: bad file descriptor" |
105 |
> > time="2017-10-24T04:42:39.885161875+02:00" level=info msg="Default |
106 |
> > bridge (docker0) is assigned with an IP address 172.17.0.0/16. |
107 |
> > Daemon option --bip can be used to set a preferred IP address" |
108 |
> > time="2017-10-24T04:42:39.885339857+02:00" level=error msg="failed |
109 |
> > to set to initial namespace, readlink /proc/4588/task/4588/ns/net: |
110 |
> > no such file or directory, initns fd -1: bad file descriptor" Error |
111 |
> > starting daemon: Error initializing network controller: Error |
112 |
> > creating default "bridge" network: Failed to program NAT chain: |
113 |
> > Failed to inject DOCKER in PREROUTING chain: iptables failed: |
114 |
> > iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL |
115 |
> > -j DOCKER: iptables: No chain/target/match by that name. |
116 |
> > |
117 |
> > ...and now I really did not know how to hack further... |
118 |
> > |
119 |
> > Any help is very appreciated... |
120 |
> > |
121 |
> > Cheers |
122 |
> > Meino |
123 |
> > |
124 |
> |
125 |
> You might need CONFIG_NF_NAT_IPV4 configured in your kernel to get the |
126 |
> NAT table for iptables (-t nat) |
127 |
|
128 |
The emerge should print/log which kernel options you do not have and |
129 |
should have enabled if I am not mistaken. Docker uses some advanced |
130 |
kernel features. I forgot to mention to check the kernel config in |
131 |
my quick start, sorry. |
132 |
|
133 |
Robert |
134 |
|
135 |
|
136 |
-- |
137 |
Róbert Čerňanský |
138 |
E-mail: openhs@×××××××××.com |
139 |
Jabber: hs@××××××.sk |