Absolutely, Docker's incremental buildup generates a lot of incremental layers for sure. Usual care+feeding applies.
This particular case didn't cause too much waste it seems. I flattened the image per the instructions in the link you provided and it only saved 1% of the size, so I guess that's good. Most of the size of the growth was all the apt-get installations to get the additions to the very small baseline debian installed.
debian:latest is the base debian starting point. weebian:latest is where I got to at the end. weebian:flattened is the flattened version of the same end state, which I suppose would be a good starting point for other images/containers adding extensions or the like. Docker is pretty cool for sure.
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
weebian flattened 0b3a1b145cfc 3 minutes ago 320.8 MB
weebian latest 62ae86bf4f67 19 hours ago 323.6 MB
debian latest 4d6ce913b130 5 days ago 84.98 MB
Here's a cool command to show what layer added how much size...
IMAGE CREATED CREATED BY SIZE
62ae86bf4f67 19 hours ago /bin/sh -c #(nop) CMD [/usr/bin/supervisord] 0 B
6a306f809ec0 19 hours ago /bin/sh -c #(nop) COPY file:48a3344b2449be6d3 270 B
0989d2e35ee6 19 hours ago /bin/sh -c mkdir /var/run/sshd 0 B
8bf2e2cb815f 19 hours ago /bin/sh -c echo "root:root" | chpasswd 627 B
e4c8f47ac182 19 hours ago /bin/sh -c ln -s /usr/share/nginx/www /home/w 20 B
9a6a01a4b259 19 hours ago /bin/sh -c cd weewx-* ; ./setup.py build ; ./ 5.045 MB
8a8827ba7d2f 19 hours ago /bin/sh -c tar zxvf /tmp/weewx.tgz 2.824 MB
b1090ae2e466 19 hours ago /bin/sh -c cd /tmp 0 B
41bdf5ecf73e 19 hours ago /bin/sh -c apt-get install -y supervisor open 22.03 MB
7c1c401612a4 19 hours ago /bin/sh -c apt-get update; apt-get install -y 207.8 MB
73f2da403e08 19 hours ago /bin/sh -c #(nop) MAINTAINER Vince Skahan "vi 0 B
4d6ce913b130 5 days ago /bin/sh -c #(nop) CMD [/bin/bash] 0 B
d0a18d3b84de 5 days ago /bin/sh -c #(nop) ADD file:4a58c36173b61e8a7b 84.98 MB
511136ea3c5a 19 months ago 0 B