our use case is that the developers sometimes want to access the logs of crashed pods in order to see why their app crashed. That's not possible via the OpenShift Console, therefore we backup the logs of exited containers and make them accessible to the devs.
I think that this could be accomplished via aggregated logging too (could it?) but last time we tried that it turned out to be a very heavyweight solution that constantly required our attention and oversight.
Can you give us any recommendation?
Am 2016-09-19 um 15:57 schrieb Andy Goldstein:
When you delete a pod, its containers should **always** be deleted. If they are not, this is a bug.
Could you please elaborate what use case(s) you have for keeping the containers around?
On Mon, Sep 19, 2016 at 5:09 AM, v <vekt0r7 gmx net> wrote:
we have an issue with docker/openshfit.
With Openshift 1.1.4 and Docker 1.8.2 we can delete a pod via "oc delete po" and the docker container is only stopped but not deleted. That means the container is still visible via "docker ps -a", /var/lib/docker/containers/[ha
sh] still persits, "docker logs" still works etc.
With Openshift 1.1.6 and Docker 1.9.1 the docker container is sometimes DELETED when we delete a pod via "oc delete po" and sometimes it is just stopped like with Openshift 1.1.4/Docker 1.8.2.
Is there any way we can influence this? Ideally we would like "oc delete po" to just stop the pod but not delete it.
users mailing list
users lists openshift redhat c