You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Matthew Cox (JIRA)" <ji...@apache.org> on 2018/09/20 20:37:00 UTC
[jira] [Created] (ZEPPELIN-3787) %python.docker activate results in
Java Error: "No such file or directory"
Matthew Cox created ZEPPELIN-3787:
-------------------------------------
Summary: %python.docker activate results in Java Error: "No such file or directory"
Key: ZEPPELIN-3787
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3787
Project: Zeppelin
Issue Type: Bug
Components: python-interpreter
Affects Versions: 0.8.0
Environment: docker run -p 8080:8080 --rm --name zeppelin apache/zeppelin:0.8.0
Reporter: Matthew Cox
Steps to reproduce:
* Start zeppelin in a docker container via
{noformat}
docker run -p 8010:8080 --rm --name zeppelin apache/zeppelin:0.8.0{noformat}
* Create a new note
* Run [per the example in the documentation|http://zeppelin.apache.org/docs/0.8.0/interpreter/python.html#usage-1]
{noformat}
%python.docker activate gcr.io/tensorflow/tensorflow:latest{noformat}
This results in:
{noformat}
java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at org.apache.zeppelin.python.PythonDockerInterpreter.runCommand(PythonDockerInterpreter.java:198) at org.apache.zeppelin.python.PythonDockerInterpreter.pull(PythonDockerInterpreter.java:186) at org.apache.zeppelin.python.PythonDockerInterpreter.interpret(PythonDockerInterpreter.java:73) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:103) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:633) at org.apache.zeppelin.scheduler.Job.run(Job.java:188) at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:140) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)