minishift: Re-using the docker environment on Fedora 25 fails

On Fedora 25 we are unable to re-use the docker daemon, as mentioned in https://github.com/minishift/minishift/blob/master/README.md#reusing-the-docker-daemon

Steps to reproduce:

$ minishift start --iso-url file:///home/lmohanty/Downloads/minishift-centos7.iso

$ minishift docker-env
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.42.187:2376"
export DOCKER_CERT_PATH="/home/lmohanty/.minishift/certs"
export DOCKER_API_VERSION="1.24"
# Run this command to configure your shell: 
# eval $(minishift docker-env)

$ eval $(minishift docker-env)

$ docker ps
could not read CA certificate "/etc/docker/ca.pem": open /etc/docker/ca.pem: no such file or directory

Original reported as: https://github.com/minishift/minishift-centos-iso/issues/106 It is an issue in Fedora 25 and it is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1402074

Let’s keep this issue open until we have verified with a working version.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 20 (18 by maintainers)

Most upvoted comments

As a workaround you can use docker flags to point to the right certificates e.g. if you want to run docker ps you can as below command $ docker --tlscacert=/home/lmohanty/.minishift/certs/ca.pem --tlscert=/home/lmohanty/.minishift/certs/cert.pem --tlskey=/home/lmohanty/.minishift/certs/key.pem info

At the risk of repeating myself, I’ll remind that if we document that users can reuse the docker daemon with minishift and then it doesn’t work as expected with some OS, then it is our realm and we should document it as a known issue. The fix might not be up to us, but similar to the SSH issue where we are dependent on 3rd party fix but in the meantime we are stuck with broken functionality.

At the very least keep the issue open, if we don’t expect the fix to take long at least users can search existing issues when they run into trouble.

On 31 May 2017, at 15:45, Hardy Ferentschik notifications@github.com wrote:

From my side a +1 for closing it. I don’t feel this really belongs into our realm.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.