Docker Secrets Reviews and details

Social recommendations and mentions

• Docker Secrets Best Practices: Protecting Sensitive Information in Containers

  Docker has revolutionized the way we build, ship, and run applications. However, when it comes to handling sensitive information like passwords, API keys, and certificates, proper security measures are crucial. Docker secrets provide a secure and convenient way to manage sensitive data within containers. - Source: dev.to / 11 months ago

• Building my own app - design questions

  Are you using swarm mode? If so, you might want to consider using secrets. Source: over 1 year ago

• How to handle sensitive files?

  Have a look here https://docs.docker.com/engine/swarm/secrets/. Source: over 1 year ago

• Docker Secrets in Swarm

  To use a secret you have to map it during the creation of a service (in this case redis like in the documentation:. - Source: dev.to / over 1 year ago

• How to manage secrets of my deployed services?

  Using docker secrets: This seems a no brainer, however, I haven't yet fully understood the documentation entry. For example, after reading this entry I still don't know if I can use docker secrets along with my strategy of having a separate .env file containing the environment variables (and the sensitive ones being handled by docker secrets). I have to enable swarm mode and I don't fully understand the... Source: over 1 year ago

• How to work around Vercel's 4kb environment restriction

  Many platforms have sophisticated solutions for this, like AWS KMS and Docker Secrets. The idea is that these tools hold the secret in encrypted form and provides it to the application at runtime. - Source: dev.to / almost 2 years ago

• Deploy .NET app to on-prem docker swarm, what is the best way to read docker secrets in order to use credentials to log on Azure KeyVault?

  Or you can use Docker Secrets (https://docs.docker.com/engine/swarm/secrets/), there are some unofficial (aka non-Microsoft) nuget packages to handle those, or you can create your own configuration manager, which more or less should do something like this (from https://www.jamessturtevant.com/posts/Acessing-Docker-Swarm-Secrets-From-ASPNET-Core/): ``` Public string GetSecretOrEnvVar(string key) { const string... Source: almost 2 years ago

• Do you encrypt credentials in appsettings.json?

  Https://www.vaultproject.io/ or https://docs.docker.com/engine/swarm/secrets maybe? Source: about 2 years ago

• Is there any way to secure user authentication even for someone who has access to the DB?

  .env files are not secure because they are in plain text, it should be used for non sensitive config only. The secret manager should be the one injecting the environment variable. With Kubernetes, it is built in. Docker compose also have a secret manager you can use. When using a serverless service on Heroku, AWS, Google Cloud, Azure or any really they also have a sercret manager. What makes it secure is it is not... Source: about 2 years ago

• Fully Docker support Example Bot

  Creating secrets can be done in multiple ways and may differ depending on your OS. Make sure to read the Docker Documentation to find the best way on creating a secret in your situation. Source: about 2 years ago

• Real-world stories of how we’ve compromised CI/CD pipelines

  I'm considering manually storing a secret under some inaccessible directory on the host, e.g. `/root/passwords.txt`, then expose this via Docker secrets[1] to the container. Finally, in the entrypoint script, I'd set e.g. The user passwords of some SQL server, which is then run as a non-privileged user. Would that be reasonably safe? [1] https://docs.docker.com/engine/swarm/secrets/. - Source: Hacker News / over 2 years ago

• Docker-compose up error ERROR: for db Cannot create container for service db: invalid mode: /var/lib/postgresql/data

  # ------------------------------------------------------------------------------ # More resources related to this file: # [1] Overview | https://docs.docker.com/compose/ # [2] PostgreSQL | https://github.com/docker-library/docs/tree/master/postgres # [3] Node.js | https://github.com/nodejs/docker-node/blob/master/README.md#how-to-use-this-image # ------------- # More resources for your projects: # [4]... Source: over 2 years ago

• How to set PASSPHRASES in REDIS inside Dockerfile?

  Https://docs.docker.com/engine/swarm/secrets/ -- some other options here. The goal is to only have the secrets available to containers that have the right decryption keys, essentially. It's not a simple process but it is as secure as you can get. Source: over 2 years ago

• Best Practice for Saving Email Password?

  Use a secrets manager, something like this: Https://docs.docker.com/engine/swarm/secrets/. Source: over 2 years ago

• 2 Widespread Attacks on Your Containerized Environment and 7 Rules to Prevent it.

  Docker secret allows you to store your secrets outside of the image. - Source: dev.to / almost 3 years ago

• Way to hide my secrets from Linux commands like ps and others. (from non-sudo users)

  Yes, you want to use either the --env-file option or the built-in Docker secrets. The latter is harder to configure though. Source: almost 3 years ago

• How to use secrets in windows container in docker swarm

  What have you tried? Have you read the documentation at https://docs.docker.com/engine/swarm/secrets/ ? It says that there is a default location for docker secrets from where you can read them from the container. Source: almost 3 years ago

• Do Images need to be built with Secrets support in order to use them?

  You can read more here https://docs.docker.com/engine/swarm/secrets/. Source: almost 3 years ago

• #30DaysOfAppwrite: Docker Swarm Integration

  Docker secrets and Docker configs can be used to more easily control and distribute sensitive data through the swarm. - Source: dev.to / almost 3 years ago