You are not logged in.

#1 2015-02-21 06:17:12

thesamet
Member
Registered: 2006-03-18
Posts: 4

Slow docker with devicemapper on archlinux

Like others, docker has been running slowly on my system when it was using the device-mapper backend.

Seems like the kernel provided by arch does not have the aufs modules built.

I looked into btrfs, got docker working on top of it and speed was substantially faster. However, kernel panics became a daily thing once I started using btrfs, which is unacceptable.

Is anyone using docker with archlinux? If it works well for you - what's your set up and how did you get there...

Last edited by thesamet (2015-02-21 06:17:41)

Offline

#2 2015-02-21 09:08:56

progandy
Member
Registered: 2012-05-17
Posts: 5,190

Re: Slow docker with devicemapper on archlinux

I don't use it, but you could try the overlay or zfs backend.


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#3 2015-02-21 16:08:22

firecat53
Member
From: Lake Stevens, WA, USA
Registered: 2007-05-14
Posts: 1,542
Website

Re: Slow docker with devicemapper on archlinux

I've been using Docker heavily on my server (primarily as a media server) for close to a year now. It's running on btrfs and has been completely happy, even under fairly heavy load. Stock archlinux, with almost everything running in containers. Definitely stay away from devicemapper!

systemd-+-agetty
        ├apcupsd---2*[{apcupsd}]
        ├bash---docker---4*[{docker}]
        ├dbus-daemon
        ├─docker─┬─btsync───6*[{btsync}]
        │        ├─13*[docker───4*[{docker}]]
        │        ├─7*[docker───5*[{docker}]]
        │        ├─docker───7*[{docker}]
        │        ├─docker───6*[{docker}]
        │        ├─python───19*[{python}]
        │        ├─python───12*[{python}]
        │        ├─sabnzbdplus───32*[{sabnzbdplus}]
        │        ├─start.sh─┬─java───63*[{java}]
        │        │          └─tail
        │        ├─start.sh─┬─avahi-daemon───avahi-daemon
        │        │          ├─dbus-daemon
        │        │          └─start_pms───Plex Media Serv─┬─Plex DLNA Serve───8*[{Plex DLNA Serve}]
        │        │                                        ├─python───12*[{python}]
        │        │                                        └─16*[{Plex Media Serv}]
        │        ├─start.sh─┬─openvpn
        │        │          ├─python3───2*[{python3}]
        │        │          └─transmission-da───2*[{transmission-da}]
        │        ├─start.sh───nginx───4*[nginx]
        │        ├─start.sh─┬─python───{python}
        │        │          └─tail
        │        ├─syncthing─┬─syncthing───12*[{syncthing}]
        │        │           └─7*[{syncthing}]
        │        └─38*[{docker}]
        ├─7*[docker───4*[{docker}]]
        ├─docker───5*[{docker}]
        ├─docker───9*[{docker}]
        ├─mosh-server───bash───pstree
        ├─sshd
        ├─systemd───(sd-pam)
        ├─systemd-journal
        ├─systemd-logind
        ├─systemd-network
        ├─systemd-resolve
        ├─systemd-timesyn───{sd-resolve}
        ├─systemd-udevd
        ├─tmux───bash
        └─xinetd

I had one issue about 6 months ago with some data loss after a power failure, but I believe those have been fixed in more recent kernel/btrfs updates (and I use a UPS now).

Scott

Last edited by firecat53 (2015-02-21 16:09:38)

Offline

Board footer

Powered by FluxBB