Ben Parees
Ben Parees
from an openshift perspective the better approach is to use Secrets and have the image read the password from the mounted secret. (and in a non-openshift/k8s environment, users could still...
@hhorak yes the file gets volume-mounted there and the image can reference it.
what about if you just s2i build an image locally and docker run it? under normal circumstances, npm is being exec'd so it is what will receive the signal, i...
@andrewklau i'm not yet clear on exactly what is being proposed, but changing the ENTRYPOINT sounds like a non-starter. Since this issue seems specific to the nodejs image because of...
changes made here need to be careful not to break backwards compatibility. Depending what gets proposed we may have to only add new values, not change existing values.
@ibotty yes that's correct, you'd have to add a layer, so something like: ``` FROM centos/postgresql-94-centos7 USER root RUN command to install extension USER 26 ``` a pull to the...
the additional container feels heavy-weight, why can't you watch in the background of the existing container?
it definitely seems simpler to have the image support an init script (Which i think we already have a PR for) and allow that init script to be provided via...
> Don't use a volume for the slave data, just a plain container directory. This might be problematic, since we might not be able to do quota space accounting later....
> The least we could do would be to add a sort of .this_is_a_replica_volume and check for its existence before executing the rm. sure that seems reasonable. only wipe it...