Why one RUN? about docker-openwrt-buildroot HOT 5 CLOSED

Because I saw no need to create several storage layers and was not interested in using the build cache. I would rather get the latest stable releases for the the needed packages.

Also, from what I can tell, the cache would not be used because there's only one Dockerfile, it does not have sibling Dockerfiles for which to cache the layers.

from docker-openwrt-buildroot.

Maybe I don't get Docker. How I understand is that I could separate:

• The installation of dependencies (apt-get)
• Cloning openwrt from git
• and adding a user.
  When adding a user fails because I made a mistake in the Dockerfile, I could fix it and run build again. Because these steps are separated it wouldn't need to reinstall the dependencies and clone openwrt, because these can be retrieved from cache. This would make for a faster Dockerfile development workflow?

from docker-openwrt-buildroot.

That might be the case when working with Dockerfiles that have frequent updates, however, this is not the case.

Using build caches would also mean that if you do a new build to use the latest dependencies, those might not get updated unless you issue "--no-cache=true", this might be counter-intuitive.

from docker-openwrt-buildroot.

But, isn't that the case anyway? That it will try to get the RUN command from cache. In your case it's just one, instead of multiple?

from docker-openwrt-buildroot.

I've split the RUN command into multiple sections, the build should work better with caches now.

from docker-openwrt-buildroot.