Friday, May 29, 2015

rkt and actool

I'm in the beginning of using rkt (rocket) and actool. It's obvious to me that the docs are insufficient. While I would like to help the team out with dedicated documentation I have to get some real work done.  My latest project will likely be deployed on a CoreOS cluster. I'm looking at the Beta and Alpha branches because I will be depending on etcd 2.x and the latest rkt tools.

The best part is that both rkt and actool have been installed in the CoreOS image. I'm not sure exactly when that started but for the time being the latest Alpha (695.0.0) is good enough.
$ rkt version
rkt version 0.5.4
appc version 0.5.1+git
and
$ actool version
actool version 0.5.1
But the challenge for me is that I'm using CoreOS for development too. So while I have a fairly involved setup script I also need to install rkt and actool.
wget https://github.com/coreos/rkt/releases/download/v0.5.6/rkt-v0.5.6.tar.gz
tar xzvf rkt-v0.5.6.tar.gz
cd rkt-v0.5.6
./rkt help 
and
env GOPATH=/root/_vendor/ go get github.com/appc/spec/...
The actool installation was pretty tricky because the source did not provide this info.

There is another tool call goaci.  This tool is supposed to create aci files from your go project. This did not work for me (as yet) because I have a private project and the repos may not be smart enough to use the keys. Specially since the tool seems to be converting the git commands to use https APIs instead of git which would use the SSL keys.

UPDATE:  you have to move the contents of the rkt folder to a bin folder somewhere. In my case since I'm using the CoreOS toolbox I moved the files (rkt & stage1.aci) to the /root/bin folder.

No comments:

Post a Comment

dead pixels

I have never had a dead pixel so when I read: Small numbers (1-3) of stuck or dead pixels are a characteristic of LCD screens. These are n...