You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hoped to use the base postgresql:10 image in OpenShift (3.11) and bootstrap it using the documented life cycle hooks with ConfigMaps and/or Secrets -- without making a custom image, that is. Unfortunately that doesn't work.
process_extending_files delegates to get_matched_files which calls find with both -maxdepth 1 and -type f. OpenShift mounts the paths as symlinks to a (symlink to a) sibling directory, a bit like this:
That is, postgresql-init/00-init.sh is a symlink, which -type f excludes, pointing to a file in a subdirectory, which -maxdepth 1 excludes. Could one of these restrictions be lifted?
The text was updated successfully, but these errors were encountered:
I hoped to use the base
postgresql:10
image in OpenShift (3.11) and bootstrap it using the documented life cycle hooks with ConfigMaps and/or Secrets -- without making a custom image, that is. Unfortunately that doesn't work.process_extending_files
delegates toget_matched_files
which callsfind
with both-maxdepth 1
and-type f
. OpenShift mounts the paths as symlinks to a (symlink to a) sibling directory, a bit like this:That is,
postgresql-init/00-init.sh
is a symlink, which-type f
excludes, pointing to a file in a subdirectory, which-maxdepth 1
excludes. Could one of these restrictions be lifted?The text was updated successfully, but these errors were encountered: