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