Beaglebone Che

I am trying to run che natively on beaglebone with arch linux. I am using usb0 connected to a remote windows machine. I go to 192.168.7.2:8080 and can get the webpage to load but errors at starting workspace agent. Below is the error code I am getting. Is there an ip address I need to set in the config file?

che.properties:

machine.docker.local_node_host=NULL

machine.docker.local_node_host=192.168.7.2

I tried both of the following.

machine.docker.che_api.endpoint=http://che-host😒{SERVER_PORT}/ide/api

machine.docker.che_api.endpoint=http://192.168.7.2😒{SERVER_PORT}/ide/api

Did this per another post I saw just in case [root@alarm eclipse-che]# ls -l /var/run/docker.sock srw-rw---- 1 root docker 0 Feb 22 08:40 /var/run/docker.sock [root@alarm eclipse-che]# chmod 666 /var/run/docker.sock [root@alarm eclipse-che]# ls -l /var/run/docker.sock srw-rw-rw- 1 root docker 0 Feb 22 08:40 /var/run/docker.sock

when running JAVA_HOME=/usr/lib/jvm/java-8-openjdk/jre/ bin/che.sh --skip:uid 2016-04-19 08:32:12,778[main] [INFO ] [o.a.catalina.startup.Catalina 642] - Server startup in 598971 ms 2016-04-19 08:32:51,472[kspaceManager-0] [INFO ] [o.e.c.a.m.s.MachineManager 162] - Creating machine [ws = workspace6szmky53zekoj0xb: env = HelloBeagleBoard: machine = ws-machine] 2016-04-19 08:32:52,371[kspaceManager-0] [ERROR] [o.e.c.a.m.s.u.RecipeDownloader 82] - Removal of recipe file /usr/share/eclipse-che/tomcat/temp/recipe280953514124065759.tmp failed. 2016-04-19 08:33:00,879[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 537] - Failed writing 8192 bytes org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:402) ~[che-core-api-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:339) ~[che-core-api-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:163) ~[che-core-api-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.createMachine(WorkspaceRuntimes.java:490) ~[che-core-api-workspace-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:411) ~[che-core-api-workspace-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:368) ~[che-core-api-workspace-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:180) ~[che-core-api-workspace-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:522) ~[che-core-api-workspace-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_77] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_77] at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_77] Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.buildImage(DockerInstanceProvider.java:318) ~[che-plugin-docker-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.machine.local.interceptor.EnableOfflineDockerMachineBuildInterceptor.invoke(EnableOfflineDockerMachineBuildInterceptor.java:58) ~[che-plugin-docker-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:221) ~[che-plugin-docker-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:362) ~[che-core-api-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] ... 11 common frames omitted Caused by: java.io.IOException: Failed writing 8192 bytes at org.eclipse.che.plugin.docker.client.connection.UnixSocketOutputStream.write(UnixSocketOutputStream.java:50) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) ~[na:1.8.0_77] at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126) ~[na:1.8.0_77] at com.google.common.io.ByteStreams.copy(ByteStreams.java:74) ~[guava-18.0.jar:na] at org.eclipse.che.plugin.docker.client.connection.DockerConnection$StreamEntity.writeTo(DockerConnection.java:114) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.client.connection.UnixSocketConnection.request(UnixSocketConnection.java:53) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.client.connection.DockerConnection.request(DockerConnection.java:85) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.client.DockerConnector.doBuildImage(DockerConnector.java:868) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.client.DockerConnector.buildImage(DockerConnector.java:214) ~[che-plugin-docker-client-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.buildImage(DockerInstanceProvider.java:310) ~[che-plugin-docker-machine-4.2.0-RC1-SNAPSHOT.jar:4.2.0-RC1-SNAPSHOT] ... 14 common frames omitted

`[root@alarm ~]# ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:88ff:fe72:1961 prefixlen 64 scopeid 0x20<link> ether 02:42:88:72:19:61 txqueuelen 0 (Ethernet) RX packets 22 bytes 1544 (1.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 89 bytes 6572 (6.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 84:eb:18:e5:4e:0a txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 175

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 107 bytes 8277 (8.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 107 bytes 8277 (8.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.7.2 netmask 255.255.255.0 broadcast 192.168.7.255 inet6 fe80::fcfa:1dff:fe73:5d1a prefixlen 64 scopeid 0x20<link> ether fe:fa:1d:73:5d:1a txqueuelen 1000 (Ethernet) RX packets 621105 bytes 843986329 (804.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 140937 bytes 20853497 (19.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 `

[james10174]

Got it into workspace and created project! Having other issues but will post another bug for that.

[james10174]

Sorry to keep posting on this bug listing but another thing that might interest others using arm is docker arm emulation on windows 8+. My thought is that you can have a windows che server that compiles and then sends docker container to arm sbc such as beaglebone or raspberry pi via scp. Then run command in che that starts docker container on sbc. I am pretty new with docker and che so sorry if I am saying anything incorrect in the process. One of the biggest headaches with arm development is how slow compile times are and dealing with cross compiling. I will of course keep everyone posted on my progress. http://blog.hypriot.com/post/close-encounters-of-the-third-kind/