https://bugzilla.redhat.com/show_bug.cgi?id=1156654
Bug ID: 1156654
Summary: Cannot start docker
Product: Fedora
Version: 21
Component: docker-io
Severity: high
Assignee: lsm5(a)fedoraproject.org
Reporter: znmeb(a)znmeb.net
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem: 'sudo systemctl start docker' fails to start service.
Version-Release number of selected component (if applicable): docker-io.x86_64
1.3.0-1.fc21 @updates-testing
Steps to Reproduce:
1. Install Fedora 21 and docker-io
2. Type 'sudo systemctl start docker'
Actual results:
$ sudo systemctl start docker
Job for docker.service failed. See "systemctl status docker.service" and
"journalctl -xe" for details.
$ systemctl status docker.service -l
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
Active: failed (Result: exit-code) since Fri 2014-10-24 16:34:16 PDT; 25s
ago
Docs:
http://docs.docker.com
Process: 19636 ExecStart=/usr/bin/docker -d -H fd:// $OPTIONS
$DOCKER_STORAGE_OPTIONS (code=exited, status=1/FAILURE)
Main PID: 19636 (code=exited, status=1/FAILURE)
Oct 24 16:34:16 AlgoCompSynth docker[19636]: [c9c8a325] +job
init_networkdriver()
Oct 24 16:34:16 AlgoCompSynth docker[19636]: Unable to enable network bridge
NAT: iptables failed: iptables --wait -I POSTROUTING -t nat -s 172.17.42.1/16 !
-o docker0 -j MASQUERADE: iptables v1.4.21: can't initialize iptables table
`nat': Table does not exist (do you need to insmod?)
Oct 24 16:34:16 AlgoCompSynth docker[19636]: Perhaps iptables or your kernel
needs to be upgraded.
Oct 24 16:34:16 AlgoCompSynth docker[19636]: (exit status 3)
Oct 24 16:34:16 AlgoCompSynth docker[19636]: [c9c8a325] -job
init_networkdriver() = ERR (1)
Oct 24 16:34:16 AlgoCompSynth docker[19636]: 2014/10/24 16:34:16 (exit status
3)
Oct 24 16:34:16 AlgoCompSynth systemd[1]: docker.service: main process exited,
code=exited, status=1/FAILURE
Oct 24 16:34:16 AlgoCompSynth systemd[1]: Failed to start Docker Application
Container Engine.
Oct 24 16:34:16 AlgoCompSynth systemd[1]: Unit docker.service entered failed
state.
Oct 24 16:34:16 AlgoCompSynth systemd[1]: docker.service failed.
$ journalctl -xe
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_conntrack_tuple_
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_ct_iterate_clean
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_conntrack_alter_
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_ct_free_hashtabl
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
__nf_ct_ext_add_len
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_ct_untracked_sta
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_conntrack_hash_r
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_ct_l3proto_try_m
Oct 24 16:34:16 AlgoCompSynth kernel: nf_nat: Unknown symbol
nf_ct_alloc_hashtab
Oct 24 16:34:16 AlgoCompSynth docker[19636]: [c9c8a325] -job
init_networkdriver(
Oct 24 16:34:16 AlgoCompSynth docker[19636]: 2014/10/24 16:34:16 (exit status
3
Oct 24 16:34:16 AlgoCompSynth systemd[1]: docker.service: main process exited,
c
Oct 24 16:34:16 AlgoCompSynth systemd[1]: Failed to start Docker Application
Con
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Oct 24 16:34:16 AlgoCompSynth systemd[1]: Unit docker.service entered failed
sta
Oct 24 16:34:16 AlgoCompSynth systemd[1]: docker.service failed.
Oct 24 16:34:16 AlgoCompSynth sudo[19624]: pam_unix(sudo:session): session
close
Expected results: Docker starting
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.