These are chat archives for azukiapp/azk

27th
Aug 2015
Slobodan Mišković
@slobo
Aug 27 2015 16:23
Hi folks, on Ubuntu 14.04, I'm unable to upgrade azk. apt-get says The following packages have been kept back: azk and aptitude gives a reason: The following packages have unmet dependencies: azk : Depends: docker-engine which is a virtual package.. Do you think it's something on my end or did package dependencies get out of whack?
(the above is regarding 0.14.5 -> 0.14.6 upgrade)
Felipe Arenales Santos
@fearenales
Aug 27 2015 19:30
hi @slobo! This is because docker's repo has been renamed.. I think it's a good idea to update docker first, by running curl -sSL https://get.docker.com/ | sh
Slobodan Mišković
@slobo
Aug 27 2015 21:14
so azk no longer works with docker bundled with 14.04?
Felipe Arenales Santos
@fearenales
Aug 27 2015 21:21
it does. the only point is that we've updated the azk deb package dependencies to reflect docker changes. if you intend to upgrade azk, you should upgrade docker first or the dependencies will mismatch.
if you want to use the latest version of azk with the current version of docker, i think this isn't possible via package manager (due this change on Docker's repo name)
Slobodan Mišković
@slobo
Aug 27 2015 21:26
you are referring to Docker distributed via https://apt.dockerproject.org/, correct?
ok, now it makes sense, I checked fresh 14.04 install and ubuntu only ships docker 1.0
that would not do.
(this server went through multiple updates so I got confused where docker was coming from)
Felipe Arenales Santos
@fearenales
Aug 27 2015 21:29
oh I see
Slobodan Mišković
@slobo
Aug 27 2015 21:31
out of curiosity: you basically ship an entire nodejs embedded with azk, are there any plans to rely on system packages, or did that produce too much headache?
Felipe Arenales Santos
@fearenales
Aug 27 2015 21:47

that's not our intention. There are several reasons to not do this:

  • we wanna have the control over the version of node to run azk (and maybe that version isn't available for the user's distro);
  • we cannot assume all distros keep the node package up-to-date;
  • the user doesn't even need to know what's node to use azk;

the user shouldn't have to worry about nothing but azk.

Slobodan Mišković
@slobo
Aug 27 2015 21:50
makes sense. do you find you upgrade node with each version, or would extracting it into azk-runtime-deps be a possibility so that one doesn't have to re-download it for every release? (not that it's a big deal to download 25MB for every release, just my OCD :) )
Felipe Arenales Santos
@fearenales
Aug 27 2015 21:58
hmm.. that's a good idea. We're going to consider this in our next releases ;) thank you @slobo ! :)
Slobodan Mišković
@slobo
Aug 27 2015 22:01
welcome. that said, I would't spend much time on it unless you really find the package size to be a problem, you probably have bigger fish to fry :D
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:02
our inspiration for doing this way is from the people who made riak. they said: nowadays, it's better one download 25MB and it works than download a part, then need to download something more, then one more bit, etc. and that could not work as expected.
Slobodan Mišković
@slobo
Aug 27 2015 22:05
sounds very reasonable, added complexity would need a very good justification. Say saving you a lot of money on bandwith, in which case just put the packages on a free CDN or behind something like cloudflare.
Slobodan Mišković
@slobo
Aug 27 2015 22:33
Does azk 0.14.6 support docker 1.8?
I'm getting azk: Error: HTTP code is 500 which indicates error: server error - json: cannot unmarshal string into Go value of type bool
this worked fine before I updated docker and azk
azk: ✓ checking `azkbuild/b05a5101bd-drupal:4ee4f04ae2da15af210a9a10af19d21f24dbfaca` image...
azk: Error: HTTP code is 500 which indicates error: server error - json: cannot unmarshal string into Go value of type bool

azk:     at /usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:208:17
azk:     at getCause (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:236:7)
azk:     at [object Object].Modem.buildPayload (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:207:5)
azk:     at IncomingMessage.<anonymous> (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:183:14)
azk:     at IncomingMessage.emit (events.js:117:20)
azk:     at _stream_readable.js:944:16
azk:     at process._tickCallback (node.js:442:13)
azk: Due to the above error azk will stop all instances already running.
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:35
that's odd.. I'm checking it
1 min
Slobodan Mišković
@slobo
Aug 27 2015 22:36
note that this uses dockerfile, not a docker image
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:40
did you restart docker daemon?
Slobodan Mišković
@slobo
Aug 27 2015 22:40
yes, restarted whole machine after upgrade
interesting, seems agent wasn't started or it exited in the meantime.
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:42
azk agent you mean?
Slobodan Mišković
@slobo
Aug 27 2015 22:43
yes, cause now when I retried it asked to start agent again
maybe it's jenkins killing the agent since it was starting it, so we can ignore that
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:44
did it work? has azk been started?
Slobodan Mišković
@slobo
Aug 27 2015 22:45
no, still the same
are there any logs I can send you other than what showed up above?
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:47
i don't think so
Slobodan Mišković
@slobo
Aug 27 2015 22:47
ah, i had docker_extra: {start: {Privileged: "true"}} in my Azkfile.js. Removing that lets it start
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:48
hmm, I'll make some tests here
Slobodan Mišković
@slobo
Aug 27 2015 22:48
I think the reason I have that is that I seen it in documentation for your php image, why is (was) it needed fro that image, do you remember?
Felipe Arenales Santos
@fearenales
Aug 27 2015 22:50
try to remove quotes: docker_extra: {start: {Privileged: true}}
Slobodan Mišković
@slobo
Aug 27 2015 23:01
Aha! It works without quotes.
Felipe Arenales Santos
@fearenales
Aug 27 2015 23:01
:D
i don't see it in documentation any more (Privileged: "true") but may be lurking in other places like above
do you know why that option is needed?
Felipe Arenales Santos
@fearenales
Aug 27 2015 23:06
I'll ask @gullitmiranda to change this
I confess I don't know, but @gullitmiranda may help
Slobodan Mišković
@slobo
Aug 27 2015 23:07
thanks
Felipe Arenales Santos
@fearenales
Aug 27 2015 23:18
you're welcome!