« Previous 1 2 3
Best practices when working with Docker images
Shipshape
Conclusions
I have presented just a few of the best practices you might want to consider when working with Docker images and containers. If they seem too complicated, at least stick to vulnerability scans – these are mandatory in all scenarios. Don't think that because you are not using full systems like virtual machines you are safe: Hackers are increasingly attacking container infrastructure, including Kubernetes. Making sure your images don't contain any malicious code or grave vulnerabilities is an important part of keeping your setup secure.
Infos
- Docker Bench for Security: https://www.cisecurity.org/benchmark/docker
- Trivy: https://github.com/aquasecurity/trivy
« Previous 1 2 3
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
US / Canada
UK / Australia
Related content
-
Update your Docker containers safely
A scripted approach lets you know when to update your Docker containers. -
Securing containers with Anchore
Anchore produces a detailed analysis of your container images for known vulnerabilities in your application and operating system packages. - Docker Desktop Comes to Linux
-
Dockerizing Legacy Applications
Sooner or later, you'll want to convert your legacy application to a containerized environment. Docker offers the tools for a smooth and efficient transition. -
Test your containers with the Docker Desktop one-node cluster
The built-in single-node Kubernetes cluster included with Docker Desktop is a handy tool for testing your container.
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Most Popular
Support Our Work
ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.
