Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Slobodan Mišković
    @slobo

    hi folks, is it possible to do something like this:

        mounts: {
          '/root/.aws': path("~/.aws"),
        },

    And have it resolve ~ to current user's home folder? I tried "$HOME/.aws" as well. This is so that I can share my AWS credentials with the image so that every developer just has to configure them once on their system, so if you have suggestions for that it would be good too

    Gullit Miranda
    @gullitmiranda
    hi @slobo
    Unfortunately azk is not yet able to extend environment variables, but are in backlog. (not yet added the issue also :( )
    But there is an alternative: D
    you can use env.HOME
    Slobodan Mišković
    @slobo
    hm, i tried path("#{env.HOME}/.aws"), but gave an error, let me try what you showed - i guess string interpolation happens when env is already out of scope...
    ok great, path(env.HOME + '/.aws') works. thanks for the quick help
    Gullit Miranda
    @gullitmiranda
    :D
    Slobodan Mišković
    @slobo
    now to figure out why aws-cli now sends wrong credentials :)
    Gullit Miranda
    @gullitmiranda
    We know it's not ideal, but for now it works. If you want to (and can) open the issue, I would appreciate it: D
    what’s?
    Slobodan Mišković
    @slobo
    i see, i had old version of aws-cli in the container
    Gullit Miranda
    @gullitmiranda
    updating work?
    Slobodan Mišković
    @slobo
    fixing the config file to old format worked :)
    Gullit Miranda
    @gullitmiranda
    :smile: less bad!
    Slobodan Mišković
    @slobo
    #465 posted, thanks
    Gullit Miranda
    @gullitmiranda
    you are welcome.
    you saw the news of 0.14.0?
    Slobodan Mišković
    @slobo
    have newsletter open in another tab, waiting for a quiet moment to go over it :smile:
    Gullit Miranda
    @gullitmiranda
    nice, then it would feedback to know felt performance improvements and also the new CLI became more enjoyable.
    :D
    Slobodan Mišković
    @slobo
    just upgraded, seems a bit faster to start. but it still takes a bit, like a second or more, for any azk command to exit after it's finished the output. Is this node.js shutdown time, or, since i've opted into sending usage statistics, am I waiting for something to be sent out? If so, how do I opt out temporarily to see if that's causing the delay?
    Gullit Miranda
    @gullitmiranda
    are the last two things we are working to improve this (and many other things) for the next version.
    to change the status tracker use azk config track-toggle
    Slobodan Mišković
    @slobo
    that has sped up the exit, i am also glad to see #472 so that I can still contribute usage information without sacrificing speed (my build system runs several azk commands in a row and this delay was quite noticable)
    Now, one of our developers is using Arch Linux and is having trouble running azk. I believe he gets "Docopt not found" errors. He tried pulling latest git and running make. Did anyone get it running on Arch? Are there any more steps needed other than this: http://docs.azk.io/en/installation/source-code.html ? Thanks
    Felipe Arenales Santos
    @fearenales
    hi @slobo ! may you ask him to run make clean && make?
    drunken-monkey
    @drunken-monkey
    Hi, @slobo 's Arch Linux user here. It seems the problem was that I used a symlink in the path instead of an alias, which confused azk. Maybe that should/could be a note in the documentation?
    Anyways, thanks for the help!
    Gullit Miranda
    @gullitmiranda

    Hello @drunken-monkey ,
    Which version of azk you are using, it is from the master?
    For this problem, after make clean; make work?

    Another thing, it was possible to install libnss-resolver and use azk smoothly on Arch Linux?

    drunken-monkey
    @drunken-monkey
    With the latest version it worked, yes, thanks!
    Gullit Miranda
    @gullitmiranda
    nice
    drunken-monkey
    @drunken-monkey
    But no, libnss-resolver did not work smoothly. I have a /usr/lib/libnss_resolve.so.2 pre-installed with the systemd package, and it doesn't seem to support configuration in /etc/resolver/.
    Gullit Miranda
    @gullitmiranda
    then the libnss-resolver that adds support for /etc/resolver. @fearenales could give a help in that?
    drunken-monkey
    @drunken-monkey
    Ah, my apologies, I thought they were the same. Bit confusing, the naming.
    Anyways, installation was a bit bumpy. At first, scons install failed because the script first goes into "build/" and then tries to download an archive to "build/…" from there.
    cd build ; ln -s . build solved that problem. It would also be good to note in the instructions, though, that you need to run the command as root. I did that, but the library file then ends up in /az/lib/– not ideal, of course. After moving it to /usr/lib/manually, though, it now seems to work fine (as far as I can tell).
    Gullit Miranda
    @gullitmiranda
    These important points you raised. We will try to improve it.
    drunken-monkey
    @drunken-monkey
    Problems again, and @slobo told me to post here: While starting the system(s) for the first time yesterday worked fine, restarting them today with azk start leads to the following error and consequent abort:
    azk: Error: HTTP code is 500 which indicates error: server error - json: cannot unmarshal string into Go value of type bool
    (I guess I shouldn't post the complete trace here?) I'm using Docker version 1:1.7.0-1 – could that be a problem?
    drunken-monkey
    @drunken-monkey
    Downgrading to Docker 1.6 solved it, so it seems it's currently incompatible with 1.7 (at least in some (edge?) cases – as said, yesterday it worked fine).
    Gullit Miranda
    @gullitmiranda

    @drunken-monkey,
    there have been changes in Docker API 1.7 and AZK has not yet been updated. We need to make this update.

    You could open an issue to report this?

    Felipe Arenales Santos
    @fearenales
    I'm sorry for my delayed answer. @drunken-monkey , thanks for your feedback. We're going to improve azk's installation process for Arch Linux asap.
    but now is everything ok?
    Slobodan Mišković
    @slobo
    @fearenales, yes it seems after downgrading docker to 1.6 we were able to use everything again on Arch. Thanks
    David BF
    @d2bit
    Hi, I'm having problems with postgres containers.
    I use several projects with postgres, but each time I restart the container I't losses the data, so I have to set it up..
    Do any of you know how to solve that? It's very annoying to wait for the seeds every day :sob:
    Felipe Arenales Santos
    @fearenales
    hi @d2bit ! Probably you're not using persistent folders to postgres
    check this Azkfile.js out and add the persistent options to the mount section of your postgres system
    David BF
    @d2bit
    yeah, I'm using that template
    Felipe Arenales Santos
    @fearenales
    and still not working?
    may you send us your Azkfile.js?
    I'm on debian8, but a colleague also is on deb8 and he has not that problem :confused: