Does node.js not include packages in opkg yet?

Theodore Borromeo

@Boken-Lin @Lazar-Demin
from borromeotlhs/onion-omega:v1

is now available for use in a Dockerfile. it'll contain the entirety of the toolchain per your cross compile environment setup guide.

Regards,
TJ

Boken Lin

@Theodore-Borromeo This is fantastic! We'll put it up on our website so that everyone can use it to compile their firmwares

Theodore Borromeo

@Boken-Lin That's fine, but I still haven't compiled a thing with it!! Can anyone test it to compile some drivers and stuff?

Boken Lin

@Theodore-Borromeo I will test it out when we are doing our own compilation stuff. BTW, would you be able to write a simple tutorial in markdown showing the steps to get the image up and running on Docker? I think it can be a really useful thing to have on our wiki!

Theodore Borromeo

@Boken-Lin Assuming you know how to use docker, there are only a few ways to run it:

1.) Pull the image from docker hub and run an interactive console. e.g.:
docker pull borromeotlhs/onion-omega:v1
docker run -it 'borromeotlhs/onion-omega:v1' /bin/bash

2.) Pull the image from docker hub, reference it in your own Dockerfile 'FROM' line, run resultant image built from that Dockerfile. e.g.:
docker pull borromeotlhs/onion-omega:v1

<Dockerfile>
MAINTAINER joeschmoe@schmoenet.com
FROM borromeotlhs/onion-omega:v1

RUN . . .
</Dockerfile>

docker build -t 'my-new-image' .
docker run -it 'my-new-image' /bin/bash

There But yeah, let me know what repo you want me to write this out in Markdown, and I'll try to get to it.

PS
My vote for a package you all could try: https://github.com/OnionIoT/OpenWRT-Packages/tree/master/iojs

Chris Ward

@Theodore-Borromeo Is this your published docker image - https://hub.docker.com/r/borromeotlhs/onion-omega/ Is it best to start with this then?

Christopher Hiller

Has anyone had success building the iojs 2.x package?

Chris Ward

@Theodore-Borromeo I got your docker container running. Is it supposed to have node compiled, or do I still need to follow that process. As soon as I got the bash prompt I tried to get the node version, but node is not found.

➜  ~  docker run -it 'borromeotlhs/onion-omega:v1' /bin/bash
onion@2af6d87347d6:/openwrt$ ls
BSDmakefile  LICENSE   README          config  feeds       feeds.conf.default  package   scripts      target toolchain
Config.in    Makefile  appendtoconfig  docs    feeds.conf  include             rules.mk  staging_dir  tmp     tools
onion@2af6d87347d6:/openwrt$ node --version
bash: node: command not found

Theodore Borromeo

@Chris-Ward I compiled node from a completely different process than Onion's buildroot. It is also available at:
borromeotlhs/docker-onion-omega-nodejs

This image will contain the precompiled node and v8 binaries in them, I think in a folder called 'node_deploy'. That image will, I assume, have a working toolchain in it, though not entirely sure it was specifically suited to the onions hardware (tho node and v8 seem to work).

good luck!

Boken Lin

@Theodore-Borromeo Great job Theodore!

Theodore Borromeo

@Chris-Ward https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/

Chris Ward

@Theodore-Borromeo When I pull, I get a latest not found. Did you push this?

Theodore Borromeo

@Chris-Ward Uggh. I didn't push it, you're right. Please copy the Dockerfile at: https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/~/dockerfile/

into:
mydockerfile

and then run:
cd mydockerfile/
docker build -t '<yourusername>/docker-onion-omega-nodejs' .

until I get this uploaded after I build on my ancient personal machine

Theodore Borromeo

@Chris-Ward Turns out that I can't push a tag to an Automated Build, and as the build failed, I had to delete and recreate this repo.

Pushing now. . . Failed

Please try building as per above, and let me know. I'll have to rerun the build at home and push from there

Chris Ward

@Theodore-Borromeo looks like the actual dockerfile (recipe) is gone now from docker hub. Do you want to email it to me? veggie2u at cyberward.net

Theodore Borromeo

@Chris-Ward ugh. I'm an idiot

Here is the github repo the automated build was supposed to work from:
https://github.com/borromeotlhs/docker-onion-omega-nodejs/blob/master/Dockerfile

HTH,
TJ

Theodore Borromeo

@Chris-Ward @Boken-Lin @Lazar-Demin The 'v1' tag was pushed successfully last night. This is what I used to create node and libv8 binary, and they will be in the 'node_deploy' directory of this image once pulled. Keep in mind, the image is 3GB: https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/tags/

Chris Ward

Hey @Theodore-Borromeo it worked/downloaded with the command

docker pull borromeotlhs/docker-onion-omega-nodejs:v1

Sweet.

Weird that docker said that it was a legacy repository.

I can't manage to get into the container. I am trying this command from the docker file:

docker run -d --net=none --expose=[9000] -p 127.0.0.1:9004:9000 -t alljoyn-builder:production

(file says sudo, but not sure if you would need to)

For some reason I keep getting a "no matches found: --expose=[9000]" which is weird. I am wondering if it is something with my docker setup - I am using zsh not bash. I just got started with docker, and the examples all worked, but I can't launch this one.

Theodore Borromeo

@Chris-Ward you can run the image you pulled with:
docker run -it borromeotlhs/docker-onion-omega-nodejs:v1 /bin/bash

you pulled one image, and tried to run an older image via a tag that you may not have. I also tend not to bother with a daemon for build toolchains, but that's just me

Chris Ward

Yes @Theodore-Borromeo I got it running. I was just trying to follow the suggestion from the docker file. I don't get what they were trying to get at. I managed to get to a bash prompt with pretty much the same command as above. I looked around, saw how you compiled, but haven't had a chance to do anything else yet.