Hello Noah, Bastian
We found the following issue installing the `docker-ce` system package in
the latest credativ:debian:9 image with kernel version:
$ uname -a
Linux bntest0 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
GNU/Linux
Updating to kernel version 4.9.144-3 fixes the issue installing/starting
docker.
$ uname -a
Linux bntest0 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64
GNU/Linux
Below you can find the error messages found installing/starting docker:
$ sudo apt-get install -y docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker-ce is already the newest version (5:18.09.2~3-0~debian-stretch).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up docker-ce (5:18.09.2~3-0~debian-stretch) ...
update-alternatives: warning: forcing reinstallation of alternative
/usr/bin/dockerd-ce because link group dockerd is broken
Job for docker.service failed because the control process exited with error
code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon
2019-02-18 15:47:16 UTC; 27ms ago
Docs: https://docs.docker.com
Process: 19027 ExecStart=/usr/bin/dockerd -H fd:// (code=exited,
status=1/FAILURE)
Main PID: 19027 (code=exited, status=1/FAILURE)
CPU: 237ms
dpkg: error processing package docker-ce (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
If you check the service status:
$ sudo service docker status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-02-19 06:57:51 UTC;
41min ago
Docs: https://docs.docker.com
Process: 19240 ExecStart=/usr/bin/dockerd -H fd:// (code=exited,
status=1/FAILURE)
Main PID: 19240 (code=exited, status=1/FAILURE)
CPU: 285ms
Feb 19 06:57:49 bntest0 systemd[1]: docker.service: Main process exited,
code=exited, status=1/FAILURE
Feb 19 06:57:49 bntest0 systemd[1]: Failed to start Docker Application
Container Engine.
Feb 19 06:57:49 bntest0 systemd[1]: docker.service: Unit entered failed
state.
Feb 19 06:57:49 bntest0 systemd[1]: docker.service: Failed with result
'exit-code'.
Feb 19 06:57:51 bntest0 systemd[1]: docker.service: Service hold-off time
over, scheduling restart.
Feb 19 06:57:51 bntest0 systemd[1]: Stopped Docker Application Container
Engine.
Feb 19 06:57:51 bntest0 systemd[1]: docker.service: Start request repeated
too quickly.
Feb 19 06:57:51 bntest0 systemd[1]: Failed to start Docker Application
Container Engine.
Feb 19 06:57:51 bntest0 systemd[1]: docker.service: Unit entered failed
state.
Feb 19 06:57:51 bntest0 systemd[1]: docker.service: Failed with result
'exit-code'.
If you try to start the docker daemon manually:
bitnami@bntest0:~$ sudo dockerd
INFO[2019-02-19T07:39:30.932368995Z] parsed scheme: "unix"
module=grpc
INFO[2019-02-19T07:39:30.932590395Z] scheme "unix" not registered, fallback
to default scheme module=grpc
INFO[2019-02-19T07:39:30.932678495Z] parsed scheme: "unix"
module=grpc
INFO[2019-02-19T07:39:30.932733295Z] scheme "unix" not registered, fallback
to default scheme module=grpc
INFO[2019-02-19T07:39:30.934086796Z] [graphdriver] using prior storage
driver: overlay2
INFO[2019-02-19T07:39:30.953887703Z] ccResolverWrapper: sending new
addresses to cc: [{unix:///run/containerd/containerd.sock 0 <nil>}]
module=grpc
INFO[2019-02-19T07:39:30.954099403Z] ClientConn switching balancer to
"pick_first" module=grpc
INFO[2019-02-19T07:39:30.954240603Z] pickfirstBalancer:
HandleSubConnStateChange: 0xc42061a0e0, CONNECTING module=grpc
INFO[2019-02-19T07:39:30.954974603Z] pickfirstBalancer:
HandleSubConnStateChange: 0xc42061a0e0, READY module=grpc
INFO[2019-02-19T07:39:30.955096503Z] ccResolverWrapper: sending new
addresses to cc: [{unix:///run/containerd/containerd.sock 0 <nil>}]
module=grpc
INFO[2019-02-19T07:39:30.955170703Z] ClientConn switching balancer to
"pick_first" module=grpc
INFO[2019-02-19T07:39:30.955255503Z] pickfirstBalancer:
HandleSubConnStateChange: 0xc42061a390, CONNECTING module=grpc
INFO[2019-02-19T07:39:30.955716504Z] pickfirstBalancer:
HandleSubConnStateChange: 0xc42061a390, READY module=grpc
INFO[2019-02-19T07:39:31.006956223Z] Graph migration to
content-addressability took 0.00 seconds
WARN[2019-02-19T07:39:31.007695223Z] Your kernel does not support swap
memory limit
WARN[2019-02-19T07:39:31.007803623Z] Your kernel does not support cgroup rt
period
WARN[2019-02-19T07:39:31.007877323Z] Your kernel does not support cgroup rt
runtime
INFO[2019-02-19T07:39:31.008313923Z] Loading containers: start.
WARN[2019-02-19T07:39:31.063004643Z] Running modprobe bridge br_netfilter
failed with message: modprobe: ERROR: could not insert 'bridge': Unknown
symbol in module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert 'br_netfilter': Unknown symbol in module,
or unknown parameter (see dmesg)
insmod /lib/modules/4.9.0-8-amd64/kernel/net/llc/llc.ko
insmod /lib/modules/4.9.0-8-amd64/kernel/net/llc/llc.ko
, error: exit status 1
INFO[2019-02-19T07:39:31.188029990Z] 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
Error starting daemon: Error initializing network controller: Error
creating default "bridge" network: package not installed
And finally if you check dmesg:
[ 628.377282] llc: Unknown symbol pskb_trim_rcsum_slow (err 0)
[ 628.659672] llc: Unknown symbol pskb_trim_rcsum_slow (err 0)
[ 628.743581] llc: Unknown symbol pskb_trim_rcsum_slow (err 0)
[ 631.338534] llc: Unknown symbol pskb_trim_rcsum_slow (err 0)
Regards,
Tomas
On Thu, Feb 21, 2019 at 5:16 PM Bastian Blank <[email protected]> wrote:
> Hi Andrés
>
> On Wed, Feb 20, 2019 at 03:30:48PM +0000, Andrés Bono Jiménez wrote:
> > I am a Bitnami developer. We are facing issues when installing Docker
> > 18.09.02 in the current Credativ Debian 9 image in Azure. It seems the
> > latest version of the kernel fixes that incompatibility. Could you please
> > let us know if there is any ETA to update credativ:debian:9:latest to the
> > latest kernel version?
>
> We'll publish an image based on Debian 9.8 including linux 4.9.144-3 in
> the next days.
>
> However I don't know which incompatibility you mean. Searching in the
> maintainer e-mail does not bring up any bug-report. Maybe you could
> enlighten us.
>
> > Confidential - All Rights Reserved.
> > Bitnami © 2019
>
> You just wrote to a public archived mailing list and you really should
> fix your signature delimiter.
>
> Regards,
> Bastian Blank
>
> --
> Knowledge, sir, should be free to all!
> -- Harry Mudd, "I, Mudd", stardate 4513.3
>
--
Tomas Pizarro Moreno
Advanced Engineer
Bitnami
www.bitnami.com
Tel: +34 955 28 57 01 <+34%20955%2028%2057%2001>
Migrate your applications to the cloud - package, deploy, and maintain them
with Stacksmith <https://bitnami.com/stacksmith>.
Bitnami © 2019
