Skip to main content

Decrease Docker build time by using .dockerignore

Similar to the .tfignore file I blogged about yesterday, a .dockerignore file exists for Docker.

Why is this usefull?

To answer this question I have to explain a little bit how Docker works. When you are using Docker commands, there are in fact 2 components at work; a client and a daemon. The client only sends the commands to the daemon whereas the daemon does all the ‘real’ work.

One of the commands you probably used is docker build which allows you to build an image from a Dockerfile. When you execute this command the client will send all the files in the directory passed to the command to the daemon. For big projects, this can get very large resulting in slow builds as you have to wait until the client is done sending all files to the daemon.

Most of the time not all files are needed by docker build(e.g. previous bin and obj folders, your .git folder, …).  To avoid sending all these files you can create a .dockerignore file in your root directory. This works like a .gitignore file, listing the directories and files that Docker should ignore when creating the context, for example:

This can make a big difference even for small projects!

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.