Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Marc Bacvanski
@mbacvanski

Hi all, I’m trying out Yaktor following the guide on yaktor.io. When I run the command

docker run -it --rm --user node -v "$PWD":/app --entrypoint bash yaktor/node -c 'npm install yaktor && $(npm bin)/yaktor init'

I get the error

Unable to find image 'yaktor/node:latest' locally
Pulling repository docker.io/yaktor/node
docker: Tag latest not found in repository docker.io/yaktor/node.
See 'docker run --help'.

Is there something I should set up first?

Petter Graff
@pgraff
Hi Marc,
You should be able to simply pull yaktor/yaktor:latest. The node image is a building block for the other images. In Docker, the images are built incrementally and the node image is a simple Unix with Node installed that we can use as a foundation for other images that we build.
Matthew Adams
@matthewadams
I think we have a bug with respect to automatically building the tag "latest". Use tag "0.39.0" for now.
Matthew Adams
@matthewadams
FYI, DockerHub image yaktor/node now has “latest” tag.
Marc Bacvanski
@mbacvanski
Awesome - it works now :smile:
justinr1234
@justinr1234
Heads up I had an issue following the startup when on Node 6.8.1 ... Switched to 4.2.1 and am able to continue running the command ./yak gen-src gen-views start
Also looks like all subdomains of yaktor.io are not working ... such as eclipse.yaktor.io and docs.yaktor.io
Matthew Adams
@matthewadams
Good to know — thanks. We’ll look into official Node 6.x support in the future.
Yeah, you’re prolly using OpenDNS. If you switch to another dns service (like Google DNS), it should work. We’re working with AWS & OpenDNS to fix that.
justinr1234
@justinr1234
Seeing issues with the DNS ... can't get to anything by IP or by the http://www.myapp.yaktor ... any common causes? Trying to debug now ... Looks like all my containers are running properly (dns, vpn, mongo, app) (on Mac)
Matthew Adams
@matthewadams
What version of yaktor are you using? Latest is 0.60.1.
justinr1234
@justinr1234
Just pulled whatever is on github and followed tutorial here: https://github.com/SciSpike/yaktor
Just didn't know if people hit issues with connecting to the node server after getting up and running with the ./yak gen-src gen-views start
2016-11-11T17:41:26.266Z - info: server DEFAULT listening at http://www.yaktor_test.yaktor (ip 172.18.0.5)
Matthew Adams
@matthewadams
0.60.1 was released ~5 mins ago :)
Barrett Cervenka
@barrettc
Just for sanity check, are you trying to go to http://www.myapp.yaktor or http://www.yaktor_test.yaktor? In your case, it would be the latter
justinr1234
@justinr1234
latter and IP address
going to uninstall everything and restart with node 4 and see what happens
Barrett Cervenka
@barrettc
OK
justinr1234
@justinr1234
Does npm 3 hurt anything? (on my local machine)
Barrett Cervenka
@barrettc
Well everything is controlled by the container - the version of node/npm you have locally really shouldn't matter. When you run yak start, were there any errors related to soctun?
Matthew Adams
@matthewadams
If you’re using ./yak, then you only need docker to be installed. You wouldn’t be using any local npm or node version — it’s governed by our docker image.
justinr1234
@justinr1234
So ./yak interfaces to the docker image to proxy the commands?
Or should I be running that from a bash to the docker container? ... looks like I'm already inside the container? :)
Barrett Cervenka
@barrettc
./yak will start up the Docker containers for you with the required versions of everything. If you are having problems accessing the URL, can you make a gist with the output of everything from the ./yak start command and we can take a look?
justinr1234
@justinr1234
I'm still rerunning, will see what happens .... Also when I started all this with node 6 as the current version on my local machine it complained about missing grunt-browserify ... redoing this with node 4.2.1 as my current version is allows the ./yak to run properly so far
Getting rid of everything and restarting with node 4.2.1 as my current version fixed all my issues
Barrett Cervenka
@barrettc
Great, I'll talk to the other guys and see what might be getting the local and Docker versions of node confused with each other
justinr1234
@justinr1234
Hey guys, so I changed my DNS and I'm able to get to the docs now, but it appears I'm still not able to get to the Eclipse plugin
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Matthew Adams
@matthewadams
That message is seen when you view the site http://eclipse.yaktor.io in a web browser. If you enter http://eclipse.yaktor.io in the appropriate place in eclipse, you get the plugins, no problem. In eclipse, go to Main Menu\Help\Install New Software…\Work With: then enter http://eclipse.yaktor.io and you will be happy and life will be good. :)
justinr1234
@justinr1234
Any clue why I'd see libs.js:92 TypeError: Cannot read property 'flip' of undefined when using the UI version (/Switch_of_demo) and clicking the Submit button for Flip?
Matthew Adams
@matthewadams
@justinr1234 Not sure what’s going on there. You might try our other generated UI. When running on Mac, it’s at http://www.<app-name>.yaktor/<conversation-name>/test.html. If you used app name “my app”, then the demo test page will be at http://www.myapp.yaktor/demo/test.html. Hit the “connect” button, then “init all”. You’ll see the state diagrams for each agent in the conversation.
You should see this (might have to zoom out):
Screen Shot 2016-11-13 at 8.02.35 AM.png
If you click the “flip” button of demo Switch (bottom agent), you should see the agents change state:
Screen Shot 2016-11-13 at 8.03.57 AM.png
Matthew Adams
@matthewadams
FYI, https is now supported on all yaktor sites except the single-page site www.yaktor.io (AKA yaktor.io).