You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@toree.apache.org by "Gino Bustelo (JIRA)" <ji...@apache.org> on 2016/04/27 16:18:13 UTC

[jira] [Commented] (TOREE-307) make dev on Windows 10 machine

    [ https://issues.apache.org/jira/browse/TOREE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260229#comment-15260229 ] 

Gino Bustelo commented on TOREE-307:
------------------------------------

This is where the dev experience sits at the moment...

Building and Testing toree is all done locally on the host machine. The requirements are basically java and sbt.

The other targets in the make for running a test jupyter notebook are there for convenience and rely on docker. I'm a strong supporter of using docker on our build, test, and dev because it simplifies setup and makes sure people are on the same configs.

The error above is happening while the dev docker images is getting build, which is mainly use in `make dev` and `make jupyter`. Both start a docker image, installs toree and run jupyter. `dev` does it through volume mounts (faster) , 'jupyter' does a real installation of our pip package and is better suited for system testing.

> So my question is: would you have an another way to make "env" ? 

We were using Vagrant, but we are looking at removing all support of Vagrant in favor of Docker.

It seems that there is an issue running docker in Windows. If you can figure out a fix and submit a PR I would appreciate it since we mainly develop on Macs.

> make dev on Windows 10 machine
> ------------------------------
>
>                 Key: TOREE-307
>                 URL: https://issues.apache.org/jira/browse/TOREE-307
>             Project: TOREE
>          Issue Type: Bug
>    Affects Versions: 0.1.0
>         Environment: Windows 10 + Cygwin64/babun + Docker
>            Reporter: JEROME DUPOURQUE
>            Priority: Minor
>              Labels: build, newbie
>             Fix For: 0.1.0
>
>
> hello,
> I've a problem building the dev env on Windows 10 machine (it works fine now on Mac). After googling I was able to read that many users got the error "cannot enable tty mode on non tty input". According to the authors It doesn't come from Cygwin or Babun.
> So my question is: would you have an another way to make "env" ? 
> I read about SSH, but before trying figure out how it works, I would appreciate your advise.
> generated error:
> An error occurred trying to connect: open //./pipe/docker_engine: The system cannot find the file specified                                                                                                
> Makefile:82: recipe for target '.example-image' failed
> make: [.example-image] Error 1 (ignored)
> cannot enable tty mode on non tty input
> Makefile:82: recipe for target '.example-image' failed
> make: *** [.example-image] Error 1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)