Ahoj, na podpore bylo par lidi, kterym nefungoval Docker pod Debian 8, tak jsem se na to podival a bezi v poradku, jen se to musi udelat trochu sloziteji nez uvadi dokumentace Dockeru. Aby Docker fungoval, je potreba verzi 1.7+. Nize jsou kroky, kterymi jej rozhodit. 1) VpsAdmin / VPS -> Enable features -> musis zapnout (vpska se zrestartuje) 2) echo "JoinControllers=cpu,cpuacct,cpuset freezer,devices" >> /etc/systemd/system.conf 3) mount -t tmpfs tmpfs /sys/fs/cgroup mkdir /sys/fs/cgroup/freezer,devices mount -t cgroup cgroup /sys/fs/cgroup/freezer,devices -o freezer,devices mkdir /sys/fs/cgroup/cpu,cpuacct,cpuset mount -t cgroup cgroup /sys/fs/cgroup/cpu,cpuacct,cpuset/ -o cpu,cpuacct,cpuset 4) apt-get install curl -y 5) curl -sSL https://get.docker.com/ | sh (vyhodi chybu ohledne kernel modulu -> ignore a cekat :)) 6) usermod -aG docker $USER 7) vim /lib/systemd/system/docker.service -ExecStart=/usr/bin/docker -d -H fd:// +ExecStart=/usr/bin/docker -d -H fd:// -s vfs 8) systemctl daemon-reload 9) systemctl enable docker 10) systemctl start docker 11) systemctl status docker -> mel by v poradku bezet 12) test -> docker run --rm hello-world Medved
Dne 28.7.2015 v 16:46 Jiří Medvěd napsal(a):
Nize jsou kroky, kterymi jej rozhodit.
Díky, dal jsem do KB: https://kb.vpsfree.cz/navody/server/docker_debian -- Petr Krčmář vpsFree.cz
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.
Ahoj, tuším, kde je problém, můžeš mi na podporu poslat Id vpsky? Medved Dne 28. 7. 2015 9:42 PM napsal uživatel "Paladin" <paladin@jstation.cz>:
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.
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
Zdravim, rad by som rozbehal docker a narazil som na uplne rovnaky problem, dalo by sa niekde spisat riesenie? Ak treba vps id: 2763 Dakujem 2015-07-28 21:46 GMT+02:00 Jiří Medvěd <admin@jirimedved.cz>:
Ahoj, tuším, kde je problém, můžeš mi na podporu poslat Id vpsky?
Medved Dne 28. 7. 2015 9:42 PM napsal uživatel "Paladin" <paladin@jstation.cz>:
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.
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
Ahoj, tiez som sa chcel pohrat s dockerom na playground VPS, ale skoncil som uz pri kroku 1: 1) VpsAdmin / VPS → Enable features → musí se zapnout (VPS se restartuje) Akosi ho vo features nevidim.. je dostupny aj na playgrounde? Dik, Rasto [image: Vnorený obrázok 1] 2015-08-18 11:22 GMT+02:00 Viktor Hronec <zamr666@gmail.com>:
Zdravim,
rad by som rozbehal docker a narazil som na uplne rovnaky problem, dalo by sa niekde spisat riesenie? Ak treba vps id: 2763
Dakujem
2015-07-28 21:46 GMT+02:00 Jiří Medvěd <admin@jirimedved.cz>:
Ahoj, tuším, kde je problém, můžeš mi na podporu poslat Id vpsky?
Medved Dne 28. 7. 2015 9:42 PM napsal uživatel "Paladin" <paladin@jstation.cz>:
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.
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 V navodu se jeste mysli vsechny, protoze ve vpsAdminu 1.x neslo ty featury povolovat oddelene. Pro Docker je potreba ted povolovat bridge, iptables a tun/tap. /snajpa On 08/20/2015 10:17 PM, Rastislav Szabo wrote:
Ahoj,
tiez som sa chcel pohrat s dockerom na playground VPS, ale skoncil som uz pri kroku 1:
1) VpsAdmin / VPS → Enable features → musí se zapnout (VPS se restartuje)
Akosi ho vo features nevidim.. je dostupny aj na playgrounde?
Dik, Rasto
Vnorený obrázok 1
2015-08-18 11:22 GMT+02:00 Viktor Hronec <zamr666@gmail.com <mailto:zamr666@gmail.com>>:
Zdravim,
rad by som rozbehal docker a narazil som na uplne rovnaky problem, dalo by sa niekde spisat riesenie? Ak treba vps id: 2763
Dakujem
2015-07-28 21:46 GMT+02:00 Jiří Medvěd <admin@jirimedved.cz <mailto:admin@jirimedved.cz>>:
Ahoj, tuším, kde je problém, můžeš mi na podporu poslat Id vpsky?
Medved
Dne 28. 7. 2015 9:42 PM napsal uživatel "Paladin" <paladin@jstation.cz <mailto:paladin@jstation.cz>>:
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.
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlXWscAACgkQgRwOVqYrsFU/BgEA2D+Vw6yMRO+kZqNAAkdoAe9d Wnc1OB3DyA+c9pRBZVoBAKQV3ffJtkg44gkBPxgioEol/Ct7+uBNCyLDV9huQ6GX =8cjT -----END PGP SIGNATURE-----
Mohol by prosim este niekto pridat riesenie toho vyssie spominaneho problemu pri starte? Inappropriate ioctl device Tiez som sa pri tom bode zasekol s rovnakym problemom Dakujem S pozdravom Viktor On Fri, Aug 21, 2015, 07:06 Pavel Snajdr <snajpa@snajpa.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
V navodu se jeste mysli vsechny, protoze ve vpsAdminu 1.x neslo ty featury povolovat oddelene.
Pro Docker je potreba ted povolovat bridge, iptables a tun/tap.
/snajpa
On 08/20/2015 10:17 PM, Rastislav Szabo wrote:
Ahoj,
tiez som sa chcel pohrat s dockerom na playground VPS, ale skoncil som uz pri kroku 1:
1) VpsAdmin / VPS → Enable features → musí se zapnout (VPS se restartuje)
Akosi ho vo features nevidim.. je dostupny aj na playgrounde?
Dik, Rasto
Vnorený obrázok 1
2015-08-18 11:22 GMT+02:00 Viktor Hronec <zamr666@gmail.com <mailto:zamr666@gmail.com>>:
Zdravim,
rad by som rozbehal docker a narazil som na uplne rovnaky problem, dalo by sa niekde spisat riesenie? Ak treba vps id: 2763
Dakujem
2015-07-28 21:46 GMT+02:00 Jiří Medvěd <admin@jirimedved.cz <mailto:admin@jirimedved.cz>>:
Ahoj, tuším, kde je problém, můžeš mi na podporu poslat Id vpsky?
Medved
Dne 28. 7. 2015 9:42 PM napsal uživatel "Paladin" <paladin@jstation.cz <mailto:paladin@jstation.cz>>:
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.
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz <mailto:Community-list@lists.vpsfree.cz> http://lists.vpsfree.cz/listinfo/community-list
_______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iF4EAREIAAYFAlXWscAACgkQgRwOVqYrsFU/BgEA2D+Vw6yMRO+kZqNAAkdoAe9d Wnc1OB3DyA+c9pRBZVoBAKQV3ffJtkg44gkBPxgioEol/Ct7+uBNCyLDV9huQ6GX =8cjT -----END PGP SIGNATURE----- _______________________________________________ Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
On 08/21/2015 12:10 PM, Viktor Hronec wrote:
Mohol by prosim este niekto pridat riesenie toho vyssie spominaneho problemu pri starte? Inappropriate ioctl device
Tiez som sa pri tom bode zasekol s rovnakym problemom
Uhuh, vpsAdmin 2 nezapinal feature bridge. Nastav si features znovu a melo by to jit. Jakub
Dne 21.8.2015 v 07:06 Pavel Snajdr napsal(a):
V navodu se jeste mysli vsechny, protoze ve vpsAdminu 1.x neslo ty featury povolovat oddelene.
BTW: Je nějaká výhoda v tom _nemít_ některé z featur povolené? Všude zatím jen čtu, že je potřeba zapnout features, ale ještě nikdy jsem nečetl, že by pro nějakou činnost bylo potřeba vypnout features. Nebylo by tedy logičtější mít features ve výchozím stavu povoleny? -- Ondra
On 21 Aug 2015, at 14:13, Ondřej Caletka <ondrej@caletka.cz> wrote:
Dne 21.8.2015 v 07:06 Pavel Snajdr napsal(a):
V navodu se jeste mysli vsechny, protoze ve vpsAdminu 1.x neslo ty featury povolovat oddelene.
BTW: Je nějaká výhoda v tom _nemít_ některé z featur povolené? Všude zatím jen čtu, že je potřeba zapnout features, ale ještě nikdy jsem nečetl, že by pro nějakou činnost bylo potřeba vypnout features. Nebylo by tedy logičtější mít features ve výchozím stavu povoleny?
Jop, ne vsechny featury se snaseji s live migraci a podobne, nekdy muzou byt timhle zpusobem povolene veci na obtiz - napr. jakmile je povoleny NFS server, jeho live migrace neni podporovana vubec a s ostatnimi featurami se obvykle zvysuje rapidne pravdepodobnost failu pri dumpu contextu CT na disk. Zatim checkpoint/restore nepouzivame, cili je to spis do budoucna, ale obecne doporucuju nepovolovat vic, nez je potreba. /snajpa
-- Ondra
participants (8)
-
Jakub Skokan -
Jiří Medvěd -
Ondřej Caletka -
Paladin -
Pavel Snajdr -
Petr Krcmar -
Rastislav Szabo -
Viktor Hronec