{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Secrets in Docker: How to Manage Keys ","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/511299f4\"></iframe>","width":"100%","height":180,"duration":483,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/secrets-in-docker-how-to-manage-keys.\n             This article walks through the places a secret leaks in a normal Docker workflow, how to check for each one, and the two patterns that actually keep keys out \n            Check more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #docker, #docker-image, #docker-containers, #docker-security, #docker-compose, #secret-leaks, #how-to-manage-keys, #hackernoon-top-story,  and more.\n            \n            \n            This story was written by: @tnawaz. Learn more about this writer by checking @tnawaz's about page,\n            and for more stories, please visit hackernoon.com.\n            \n                \n                \n                This article walks through the places a secret leaks in a normal Docker workflow, how to check for each one, and the two patterns that actually keep keys out: BuildKit secret mounts for build time, and runtime injection for everything else. The examples use the local agent stack from my earlier Compose article, because it is a realistic case.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}