Read the article so you don’t have to:

Unlike the title suggests, the docker images they found won’t leak your credentials when you use them, but already contain the credentials of whoever created the image (p.e. through .env files that were accidentally added to the image).

While it contains the valuable reminder to avoid long lived credentials (like API - keys) or use secrets-stores, this “leak” is on the same level as accidentally pushing confidential information to github IMHO.

Fix: have both .gitignore and .dockerignore files and make sure they both contain .env. You use .env and don’t hardcode your secrets, right?

If it’s a nontechnical crowd with no intention of using this knowledge in the workplace for actual programming, I’d agree with the other poster who recommended scratch: it’s a visual, object oriented language, so there are hardly chances for typos, it’s designed for learning, it runs in the browser. It’s a great language for kids and older “first contacts”

Today’s risky click is presented by GreatTitEnthusiast 👀