Closed creativie closed 4 years ago
@creativie thanks for the report.
I believe the reason for the failure is that the hosts are missing the /etc/localtime
file, so the container engine when detects that it's missing the source path creates a directory (I believe this is the default behavior for the engines I know) and then proceeds to do the binding, but then the binding finds that we are trying to bind a directory (the one created by the engine) with a normal file that exists within the container and fails with the error we see.
As far as I know your hosts should have /etc/localtime
. Could you confirm what do you have on your host's /etc/localtime
path please?
No
ls: cannot access '/etc/localtime': No such file or directory
OKD 4.5 beta (Fedora CoreOS) Ember-csi operator
When I add new storage backend with vsphere driver all pod become failing
I delete volume '/etc/localtime' from statefulset and daemon, after pods starts successfully