Cannot read config file when referenced through nested symbolic links #3753
Labels
theme/operator-usability
Replaces UX. Anything related to making things easier for the practitioner
type/bug
Feature does not function as expected
Milestone
Version: 1.0.1, 1.0.2
Description of the Issue (and unexpected/desired result)
Consul does not start as it's unable to read config files for the specific structure below. It works in 1.0.0.
I have a structure with symbolic links that looks like this:
This kind of structure is created by Kuberenetes when mounting volumes, see kelseyhightower/consul-on-kubernetes#23
The structure above is exactly the same as in the linked issue, except I've simplified the names.
Reproduction steps
Create a file named
Dockerfile
with the contentBuild image:
docker build -t consul-test .
See content of
/consul/config
See the content of
server.json
Start consul with
server.json
as config fileIt fails with:
To prove that it works in version 1.0.0, modify the content of
Dockerfile
to use imageconsul:1.0.0
. Build the image and start Consul:Consul will start correctly. Press
Ctrl+C
to exitTo cleanup execute
I have verified that it does not work in version 1.0.2 either. I used 1.0.1 in this example as 1.0.2 hasn't been released to Docker Hub.
The text was updated successfully, but these errors were encountered: