On Tue, Jul 19, 2016 at 08:53:22AM -0700, 'Tim Hockin' via Containers at Google wrote: > On Tue, Jul 19, 2016 at 4:41 AM, Gurvinder Singh > <[email protected]> wrote: > > On 07/19/2016 01:10 PM, Rodrigo Campos wrote: > >> Yes, it's not supported. > >> > >> The alternative I see is making /etc/passwd a Symlink. So, you mount the > >> secret in /etc/secret/ (to say something) and the container image has a > >> Symlink pointing /etc/passwd to /etc/secret/passwd. > > Well that will work, but I do not control all the container images which > > users will run. So having option to project the file can help. This is > > useful not only for passwd case but other configuration cases too where > > a program except the config file to a certain directory path with other > > files in that dir. > > > > Any plans to add this feature. > > Doing this comes with some pretty hefty restriction - specifically > that auto-updating can not work. #23748 demonstrates a technique that > should work for this.
Ohh, great trick! It's a shame the site is not updated (http://kubernetes.io/docs/api-reference/v1/definitions/#_v1_volumemount). I've already created a report for that some days ago about the same: https://github.com/kubernetes/kubernetes.github.io/issues/803 Thanks a lot, Rodrigo -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
