Painless Docker - 2nd Edition

The None Network

Some containers don't need to be attached to any network since they're meant to run isolated tasks. Some examples of such tasks include:

• Running batch jobs that don't require network access.
• ETL (Extract, Transform, Load) processes that operate on local data.
• Filesystem maintenance tasks.
• Functions that interact only with the Docker API via the Docker socket.
• Security-sensitive applications that should not have any network exposure.
• And more.

In this specific case, it's better to attach the container to the none network. This will prevent incoming and outgoing network traffic.