sOblivionsCall

@henrywhitaker3 have you considered packaging the binary as part of the container build itself? this will allow you to have strict control of what binary version is packaged and will...

> @sOblivionsCall only reason I'm not doing that is due to their license (as far as I can remember you're not allowed to distribute it) I'm surprised you were even...

Can confirm this is a bug in the latest tag of the docker container and most likely the v1.2.1 tag as they appear to have been uploaded at the same...

look at file ownership, this looks more like a permissions issue

also looking for guidance here, seeing a permission issue that i'm not sure is an easy solve as i'm also using a nfs-provisioner ``` kubectl logs nextcloud-7969756654-7j9xh --tail 50 -f...

adding more info: ``` $ kubectl describe pod nginx Name: nginx Namespace: default Node: yzen-erver/10.1.1.20 Start Time: Thu, 04 Apr 2019 21:42:21 -0500 Labels: name=nginx Annotations: kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"labels":{"name":"nginx"},"name":"nginx","namespace":"default"},"spec":{"cont... Status: Running...

for anyone who comes across this later on, changing the liveness probe to 5 seconds for the nginx timeout seems to have resolved the issue. I must have just had...

Scratch that, issue is not resolved: ``` $ kubectl describe pod nginx Name: nginx Namespace: default Node: yzen-erver/10.1.1.20 Start Time: Sun, 14 Apr 2019 13:18:10 -0500 Labels: name=nginx Annotations: kubectl.kubernetes.io/last-applied-configuration:...

It is very odd that the pod behaves perfectly find if i remove the liveness probe completely.