That never even occurred to me. Thank you sir.
On July 13, 2016 at 09:18:44, Alex Wauck (alexwauck exosite com) wrote:Your Dockerfile clobbers /run in the image. That leads to bad things. Don't feel bad; we made the same mistake.
On Wed, Jul 13, 2016 at 7:06 AM, Skarbek, John <John Skarbek ca com> wrote:
I was messing around with a random quick application on the preview of openshift 3 online. I ran into this in the log of a container that won’t start:
Timestamp: 2016-07-13 11:49:38.160398231 +0000 UTC Code: System error Message: lstat /var/lib/docker/devicemapper/mnt/704986103e760820b33944aaf09c2210b07e6b89f158f2053f3782307de89846/rootfs/run/secrets: not a directory Frames: --- 0: setupRootfs Package: github.com/opencontainers/runc/libcontainer File: rootfs_linux go 40 --- 1: Init Package: github.com/opencontainers/runc/libcontainer.(*linuxStandardInit) File: standard_init_linux go 57 --- 2: StartInitialization Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory) File: factory_linux go 242 --- 3: initializer Package: github.com/docker/docker/daemon/execdriver/native File: init go 35 --- 4: Init Package: github.com/docker/docker/pkg/reexec File: reexec go 26 --- 5: main Package: main File: docker go 18 --- 6: main Package: runtime File: proc go 63 --- 7: goexit Package: runtime File: asm_amd64 s 2232
The pod remains in a Crashloop. I fear something might be wrong with the ability handle secrets. Despite me not using any…
For reference here’s my quick and nasty docker image: https://hub.docker.com/r/jtslear/command-check/
users mailing list
users lists openshift redhat com