Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Fix tty errors using winpty #221

Merged
merged 1 commit into from Oct 7, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
30 changes: 29 additions & 1 deletion windows/start.sh
Expand Up @@ -31,4 +31,32 @@ fi

echo "Starting machine $VM..."
$DOCKER_MACHINE start $VM
$DOCKER_MACHINE ssh $VM

echo "Setting environment variables for machine $VM..."
eval "$($DOCKER_MACHINE env --shell=bash $VM)"

clear
cat << EOF


## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/

EOF
echo -e "${BLUE}docker${NC} is configured to use the ${GREEN}$VM${NC} machine with IP ${GREEN}$($DOCKER_MACHINE ip $VM)${NC}"
echo "For help getting started, check out the docs at https://docs.docker.com"
echo
cd

docker () {
winpty docker $@

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not exactly sure why, but the Git for Windows peeps explicitly call program.exe in their winpty convenience aliases. (git-for-windows/build-extra@ceda40c)

It might be less likely to run into a conflict with any other docker aliases users may set.

Do you think we should follow the {name}.exe convention?

}
export -f docker

exec "$BASH" --login -i