New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
privacyIDEA Docker image - Discussion #6
Comments
i write my option as infra structure engineer who dockerized privacyidea and running it in production with k8s/docker.
Not exactly, if projects provide official images, those are usually used. Setup things up quite often is complex and if you do yourself there is 100 ways you can go wrong. Plus using official images when/if possible is big time win also, it can take days to create/setup some more complex app into docker.
it is not actually relevant how app is running inside docker image (so use whatever you as developer of the app feel is the bext), as long as everything works.
For setup i would go with 2 things:
|
For the For the production image, we have some environmental reasons for building our own image, however it would be nice to align any common components with what you are doing. |
Since this comes up more often lately we would like to discuss the outline of a new/improved docker image.
In my understanding there are two orthogonal concepts:
In my experience if someone is using Docker in a productive environment, they build the images themselves to have better control over security and fixes.
So i would like to concentrate in this repository on the first concept, a docker-compose configuration which just runs:
Please share Your thoughts so we can get this thing on the road.
The text was updated successfully, but these errors were encountered: