Docker build takes too long -


certain instructions in dockerfiles taking long. example, adding 3 lines file add instruction or echoing line file takes more minute.

what can causing this?

here's syslog, not sure if relevant:

may 29 18:45:17 mymachine kernel: [97813.649053] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:45:54 mymachine kernel: [97850.627286] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:45:55 mymachine kernel: [97851.249484] ext4-fs (dm-4): mounted filesystem ordered data mode. opts: discard may 29 18:46:34 mymachine console-kit-daemon[983]: glib-critical: source id 5102 not found when attempting remove may 29 18:46:53 mymachine kernel: [97908.977215] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:46:53 mymachine kernel: [97909.217137] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:46:53 mymachine kernel: [97909.247252] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:47:26 mymachine kernel: [97942.607378] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:47:26 mymachine kernel: [97942.767831] ext4-fs (dm-4): mounted filesystem ordered data mode. opts: discard may 29 18:48:36 mymachine kernel: [98012.632630] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:48:37 mymachine kernel: [98013.681835] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:48:38 mymachine kernel: [98014.009612] netlink: 1 bytes leftover after parsing attributes. may 29 18:48:38 mymachine kernel: [98014.016816] device vethb49f entered promiscuous mode may 29 18:48:38 mymachine kernel: [98014.020408] ipv6: addrconf(netdev_up): vethb49f: link not ready may 29 18:48:38 mymachine kernel: [98014.046745] ipv6: addrconf(netdev_change): vethb49f: link becomes ready may 29 18:48:38 mymachine kernel: [98014.046785] docker0: port 2(vethb49f) entered forwarding state may 29 18:48:38 mymachine kernel: [98014.046791] docker0: port 2(vethb49f) entered forwarding state may 29 18:48:39 mymachine kernel: [98015.128850] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:48:39 mymachine kernel: [98015.174370] docker0: port 2(vethb49f) entered disabled state may 29 18:48:39 mymachine kernel: [98015.174860] device vethb49f left promiscuous mode may 29 18:48:39 mymachine kernel: [98015.174867] docker0: port 2(vethb49f) entered disabled state may 29 18:49:18 mymachine kernel: [98054.703978] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:49:18 mymachine kernel: [98054.834326] ext4-fs (dm-4): mounted filesystem ordered data mode. opts: discard may 29 18:50:14 mymachine kernel: [98110.408736] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:50:15 mymachine kernel: [98111.221056] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:50:15 mymachine kernel: [98111.443577] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:50:44 mymachine kernel: [98140.675447] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:50:44 mymachine kernel: [98140.695348] ext4-fs (dm-4): mounted filesystem ordered data mode. opts: discard may 29 18:51:36 mymachine kernel: [98192.027431] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:51:36 mymachine kernel: [98192.559271] ext4-fs (dm-2): mounted filesystem ordered data mode. opts: discard may 29 18:51:36 mymachine kernel: [98192.800718] netlink: 1 bytes leftover after parsing attributes. may 29 18:51:36 mymachine kernel: [98192.881484] device veth000f entered promiscuous mode may 29 18:51:36 mymachine kernel: [98192.881966] ipv6: addrconf(netdev_up): veth000f: link not ready may 29 18:51:36 mymachine kernel: [98192.945999] ipv6: addrconf(netdev_change): veth000f: link becomes ready may 29 18:51:36 mymachine kernel: [98192.946045] docker0: port 2(veth000f) entered forwarding state may 29 18:51:36 mymachine kernel: [98192.946051] docker0: port 2(veth000f) entered forwarding state may 29 18:51:37 mymachine kernel: [98193.274007] docker0: port 2(veth000f) entered disabled state may 29 18:51:37 mymachine kernel: [98193.275061] device veth000f left promiscuous mode may 29 18:51:37 mymachine kernel: [98193.275068] docker0: port 2(veth000f) entered disabled state may 29 18:51:37 mymachine kernel: [98193.319695] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:52:17 mymachine kernel: [98233.520926] ext4-fs (dm-3): mounted filesystem ordered data mode. opts: discard may 29 18:52:17 mymachine kernel: [98233.608787] ext4-fs (dm-4): mounted filesystem ordered data mode. opts: discard 

docker info:

containers: 2 images: 172 storage driver: devicemapper  pool name: docker-202:1-1447309-pool  data file: /var/lib/docker/devicemapper/devicemapper/data  metadata file: /var/lib/docker/devicemapper/devicemapper/metadata  data space used: 4443.4 mb  data space total: 102400.0 mb  metadata space used: 9.4 mb  metadata space total: 2048.0 mb execution driver: native-0.2 kernel version: 3.13.0-24-generic warning: no swap limit support 

which docker backend running? aufs? device-mapper? btrfs? ...?

switching aufs backend, if operating system supports it, helpful here.

a more authoritative answer require knowing backend you're using, performance characteristics of system you're on, , perhaps trace of invocation (such sysdig can generate).


Comments

Popular posts from this blog

c++ - OpenCV Error: Assertion failed <scn == 3 ::scn == 4> in unknown function, -

php - render data via PDO::FETCH_FUNC vs loop -

The canvas has been tainted by cross-origin data in chrome only -