28 Jul
2015
28 Jul
'15
7:33 p.m.
Ahoj,
uvod chci podekovat za postup, snazil jsem se o to drive sam a moc
daleko jsem se nedostal, takze to muzu zkusit znovu dle Tveho navodu :)
On , Jiří Medvěd wrote:
10) systemctl start docker
11) systemctl status docker -> mel by v poradku bezet
Nicmene zasekl jsem se na tomto radku. Dostavam nasledujici:
● docker.service - Docker Applitation Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Active: failed (Result: exit-code) since Tue 2015-07-28 21:23:21
CEST; 3s ago
Docs: https://docs.docker.co
Process: 1017 ExecStart=/usr/bin/docker -d -H fd:// -s vfs
(code=exited, status=1/FAILURE)
Main PID: 1017 (code=exited, status=1/FAILURE)
Jul 28 21:23:21 hostname systemd[1]: Started Docker
Applitation Container Engine.
Jul 28 21:23:21 hostname docker[1017]:
time="2015-07-28T21:23:21.671678919+02:00" level=warning
msg="You are running linux kernel version
2.6.32-042stab108.5, which might be unstable running
docker. Please upgrade your kernel to 3.10.0."
Jul 28 21:23:21 hostname docker[1017]:
time="2015-07-28T21:23:21.674020403+02:00" level=warning
msg="Running modprobe bridge nf_nat failed with message: ,
error: exit status 1"
Jul 28 21:23:21 hostname docker[1017]:
time="2015-07-28T21:23:21.686320125+02:00" level=fatal
msg="Error starting daemon: Error initializing network
controller: Error creating default \"bridge\" network:
inappropriate ioctl for device"
Jul 28 21:23:21 hostname systemd[1]: docker.service: main
process exited, code=exited, status=1/FAILURE
Jul 28 21:23:21 hostname systemd[1]: Unit docker.service
entered failed state.
Nasel jsem na githubu bug se stejnym popisem, ale co jsem pochopil, tak
v 1.7.1 by to jiz melo byt opravene. Nema nekdo nejaky napad, kde by
mohl byt problem pripadne alespon co bych mohl zkusit?
Diky
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.