Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Luiz Paulo Camargo
    @luizpcam
    Hi @slobo , this error is happening with me too. But azk team is fixing it. Here is The issue: The workaround is pull direct from docker like this: adocker
    Try this command and start azk again : adocker pull lop
    Slobodan Mišković
    @slobo
    thanks @luizpcam. Good to know I'm not crazy. Doing the pull and start works, bug unfortunately our CI process needs the -B for other custom images.
    I am probably just going to inline all the images we use into local Dockerfiles, hub is not always reliable it seems
    Luiz Paulo Camargo
    @luizpcam
    Yeah! Me too! only we have to do is wait for new version!
    Slobodan Mišković
    @slobo
    I take it that -B does some sort of lookup before doing a docker pull - maybe a simple fix is to always just issue a docker pull when -B is specified - I mean it will end in no-op anyways if image is up to date - not sure it's an optimization to do any pre-checks (I'm probably naíve about some usecases)...
    Luiz Paulo Camargo
    @luizpcam
    I agree maybe this solution works great
    Slobodan Mišković
    @slobo
    this ugly fix makes it work on my computer at least: azukiapp/azk#676
    (we lose progressbar instead of aborting the entire process)
    Gullit Miranda
    @gullitmiranda
    hi @slobo and @luizpcam. tks for PR @slobo.
    I'm going to work on changing the lib of communication with the docker. it is not a simple task for this has been delayed until the time. But now became an impediment.
    Gullit Miranda
    @gullitmiranda
    @slobo, instead of using console.log we can use the log (like this https://github.com/azukiapp/azk/blob/master/src/cmds/scale.js#L99). would you prefer to do the change or change in the merge?
    Slobodan Mišković
    @slobo
    @gullitmiranda it would be great you bring it up to standard, I won't have time to look at it for a few days. thanks
    Gullit Miranda
    @gullitmiranda
    Nice. I do
    Wesley Victhor Mendes Santiago
    @wesleyvicthor
    hey guys, I am using the php-fpm image and I cannot restart nginx properly
    service nginx restart does not output any error. it just stands.
    nginx service start neither.
    Leandro Lugaresi
    @leandro-lugaresi
    hey guys!
    Anyone using php-apache?
    Gullit Miranda
    @gullitmiranda
    @leandro-lugaresi, any questions?
    Andreas Schmelas
    @m9dfukc
    Hello, how is it going?
    Any progress releasing version 0.19.0?
    And how about the progress integrating docker for osx?
    ... I know I'm asking for a lot ;)
    Slobodan Mišković
    @slobo
    seems docker for osx and windows is publicly released: https://blog.docker.com/2016/07/docker-for-mac-and-windows-production-ready/
    Danni Friedland
    @BlueHotDog
    hey guys, trying to install AZK on newest mac, encountering a LOT of errors :(
    Danni Friedland
    @BlueHotDog
    ?
    Gullit Miranda
    @gullitmiranda
    hi @BlueHotDog. we are working to release a version using the docker for mac. After the upgrade we hope not to occur errors in Mac Sierra.
    Danni Friedland
    @BlueHotDog
    Anyway i can make AZK work now?
    my current error is:
    ```
    azk: Lost internet connection or error while connecting to docker registry:
    azk: Error: 404: >> url: https://registry-1.docker.io/v1/repositories/library/rabbitmq/tags/3.6.5-management
    @gullitmiranda
    Gullit Miranda
    @gullitmiranda
    @BlueHotDog this error has been solved in master branch. We need make new release with this (and others) fixes.
    Danni Friedland
    @BlueHotDog
    @gullitmiranda Anyway i can run from master? it's kind of urgent since i'm unable to provision my environment for the past 2 days :(
    Gullit Miranda
    @gullitmiranda
    yes. you can run from master.
    instructions here: http://docs.azk.io/en/installation/source-code.html
    sorry for this problems. we had to prioritize some of the Azuki tasks, so the azk was a little stopped, mainly by the size of the work we are doing to the azk support the docker for mac
    Slobodan Mišković
    @slobo
    hey folks, is there a place to adjust the timeout for requests going through hipache?
    Slobodan Mišković
    @slobo

    eg, say I have php webserver at php.dev.azk.io and i have sleep.php <?php sleep(65);. Compare these two:

    ⟩ time curl -v http://php.dev.azk.io/sleep.php
    ...
    * Empty reply from server
    curl: (52) Empty reply from server
    Command exited with non-zero status 52
    0.00user 0.00system 0:30.02elapsed

    vs going to the container directly

    time curl -v http://php.dev.azk.io:32791/sleep.php
    ...
    < HTTP/1.1 200 OK
    ...
    
    0.00user 0.00system 1:05.00elapsed
    you can see that if ballancer is involved, it terminates connection after 30 seconds, vs webserver will let it run to completion
    Slobodan Mišković
    @slobo
    i see, we need to change tcpTimeout in balancer.js. I've sent in a pull request that lets us do this (and also other interesting hipache configs) via AZK_BALANCER_... environment vars: azukiapp/azk#689
    Gullit Miranda
    @gullitmiranda
    hi @slobo . tks for the contribution.
    I already gave my LGTM
    Slobodan Mišković
    @slobo
    thanks for accepting the other change!
    I have a question regarding azk shell behaviour and changing the window size.
    It seems that we don't forward SIGWINCH to the process running in the shell
    Slobodan Mišković
    @slobo
    how does azk shell work - does it end up exec(3)ing docker run or does it somehow proxy between docker process and the terminal?
    problem right now with window sizing is that if I start a azk shell, and then resize the terminal window, process inside is not aware and even entering bash commands turns into a pain
    Slobodan Mišković
    @slobo
    ah, found it azukiapp/azk#690
    seems on resize we were trying to get width of stderr instead of stdout
    (this could be a bug with node?)
    Slobodan Mišković
    @slobo
    would it make sense to make azk shell container cleanup not yield and instead let it fire in the background? It causes 0.5-1s delay when exiting shell while we wait for docker to clean the container, but from user perspective I don't think anyone cares as long as it gets cleaned up in the end?