Skip to content
This repository was archived by the owner on Feb 27, 2018. It is now read-only.
This repository was archived by the owner on Feb 27, 2018. It is now read-only.

boot2docker shellinit on Windows prints commands that can not be used in cmd.exe or in a cygwin terminal #301

@gmlewis

Description

@gmlewis

Did the output from boot2docker shellinit change recently on Windows?

We used to not require cygwin, correct? With v1.3.0, I get:

> boot2docker shellinit
Writing C:\Users\gmlewis\.boot2docker\certs\boot2docker-vm\ca.pem
Writing C:\Users\gmlewis\.boot2docker\certs\boot2docker-vm\cert.pem
Writing C:\Users\gmlewis\.boot2docker\certs\boot2docker-vm\key.pem
    export DOCKER_CERT_PATH=C:\Users\gmlewis\.boot2docker\certs\boot2docker-vm
    export DOCKER_TLS_VERIFY=1
    export DOCKER_HOST=tcp://192.168.59.105:2376

export only works in a cygwin terminal... and if I run the commands, I get:

$ echo $DOCKER_CERT_PATH
C:Usersgmlewis.boot2dockercertsboot2docker-vm

So I'm guessing we first need to go back to using set or if we require cygwin, then we put the path in single quotes to that bash doesn't try to parse it. I don't remember now if v1.2.0 typed set or export, but now that there are 3 variables, it is probably more important for us to standardize on either cmd.exe or a cygwin terminal on Windows.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions