Reputation: 708
I'm using an env file which contains sensitive information for docker creation.
But the thing is they are not secure. They can be easily viewed via docker inspect, and hence they are available to any user that can run docker commands.
I'm looking for a way in which I can secure these values from the outside users, without using docker swarm.
Is there a way to achieve this?
Upvotes: 3
Views: 1523
Reputation: 3691
For variables needed in built-time (image creation):
For env variables needed when container starts:
history
inspecting your cli command.Upvotes: 2