Christoph Christoph - 3 years ago 320
PHP Question

How to add a config file in a non-empty directory of an Openshift v3 application

I deployed a PHP+postgreqsl application (TinyTiny RSS, on the new Openshift v3. On initial access you create a

from the available template, which contains DB passwords etc. to enable tt-rss to connect to the database. Now I need to add that file to the app root directory (/opt/app-root/src/) where tt-rss expects it.

Following the apparently canonical way I created a configmap with the key
and the file contents as the value. However, when mounting that config file into a volume to make it available to the application, I ran into problems as it's apparently expected that the mountpoint of the volume is a non-existing directory, so when I gave a target path of /opt/app-root/src/, my application code got overwritten.

Then, I found a way to provide a single file in an already populated directory:

you need to supply the absolute path including the filename in the mountPath and the filename again in subPath. The filename (obviously) needs to match the key in your config map.

I did that, but that leads to an inaccessible (no permissions)
file with very strange properties, see excerpt of
ls -la
in the deployed pod:

drwxrwxr-x. 8 default root 4096 Sep 29 13:41 classes
-?????????? ? ? ? ? ? config.php
-rw-rw-r--. 1 default root 8057 Sep 29 13:41 config.php-dist

is the template. What's up with the question marks?? Is this feature not working on Openshift?

The related YAML parts look like this:

- mountPath: /opt/app-root/src/config.php
name: volume-2k03m
subPath: config.php


- configMap:
defaultMode: 420
- key: config.php
path: config.php
name: tt-rss-config
name: volume-2k03m

Is there a way to fix this configuration? Is there another way to "inject" (for want of a better word) that
into the application?

Some people recommend symlinks, but I don't know how to programmatically create a symlink at the needed location without running into the same problems as with

I don't want to push it to the (public) source repo as it contains secrets and the source repo is actually an upstream repo that I would prefer not to fork and continually keep up-to-date myself.

Answer Source

Apparently, this is a current bug, see and

As a workaround, specify the subPath like this: subPath:, and everything starts to work as expected.

Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download