Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Vytenis
    @FDiskas
    I will try to change
    Gullit Miranda
    @gullitmiranda
    if you are using entrypoint, you need to make it call the following process:
    add this line in the end of file:
    exec "$@"
    Vytenis
    @FDiskas
    I messed everything :D
    Gullit Miranda
    @gullitmiranda
    :wink:
    you could do a PR adding this project to the gallery of the run project?
    Vytenis
    @FDiskas
    But its not running normaly :)
    And sure I will if I got lucky
    Gullit Miranda
    @gullitmiranda
    runned for me :D
    Vytenis
    @FDiskas
    And runs for me to but not with customized Dockerfile
    Gullit Miranda
    @gullitmiranda
    do the PR, before you agree let's take a reviewed and tested in the project, so that we can suggest or even submit improvements =D
    ok. good =D
    Vytenis
    @FDiskas
    :D Thanks
    Vytenis
    @FDiskas
    I did't get how to make pull request. Do I need just open an issue?
    Gullit Miranda
    @gullitmiranda
    for now, yes. we will improve the submission process.
    Vytenis
    @FDiskas
    Installation takes to long :)
    Gullit Miranda
    @gullitmiranda
    :D
    Slobodan Mišković
    @slobo
    hey folks, is it possible for azk start to start containers in parallel? So say if I have a system with 4 dependencies that don't depend on each other, could we get all the deps to be run at the same time, and then once they are all started we run the final system. I think it would shave off a whole bunch of time in startup for my use case.
    Do you think it would be a complicated change for azk internals?
    Gullit Miranda
    @gullitmiranda
    I think good improvement, but it is not very simple.
    This would be much simpler if the azk had a kind of state for systems
    Slobodan Mišković
    @slobo
    interesting. could you elaborate more on what kind of state management would be needed?
    Gullit Miranda
    @gullitmiranda
    we have not yet been decided how we are going to do this, but basically, we'll need to store the status of the systems somewhere. today we use the name to do this. this makes it difficult to have a sort of global status.
    well that is the implementation was made prior to docker support the notations scheme
    Slobodan Mišković
    @slobo
    Are you refering to storing the state outside of azk process?
    I would have thought that when I say azk start, it can just fire off a few docker run commands asynchronously and then wait for promises to be fulfilled and when they come back, you would fire off more docker run commands to the systems that were wating for those containers.
    I'll probably have to dig into the code to see why I'm being naive :)
    Also, how about azk stop, would that one be an easier candidate for parallelization?
    Gullit Miranda
    @gullitmiranda
    Yes. I understand your point @slobo. I'm not sure, but maybe is worth it already refactor the start process, because with the start better structured is easier to parallelize.
    Slobodan Mišković
    @slobo
    cool, thanks for your thoughts
    Andreas Schmelas
    @m9dfukc
    Hi, is there a way to omit deployment of certain containers? For example I have a node container and a postgres container both needed for development but when being deployed the postgres container should be substituted by Amzon RDS.
    Gullit Miranda
    @gullitmiranda
    @m9dfukc you can start only application and use DATABASE_URL of RDS
    use env AZK_RESTART_COMMAND to set the default start/restart command.
    Renato Biancalana da Silva
    @ReeSilva
    Guys, @gullitmiranda ask me to come here to talk with you about a bug with resolver
    *dns resolver
    About this issue azukiapp/azk#648
    Felipe Arenales Santos
    @fearenales
    hi @ReeSilva ! I'll check it and ping you back ASAP
    Renato Biancalana da Silva
    @ReeSilva
    @fearenales Ok, thx
    Felipe Arenales Santos
    @fearenales
    @ReeSilva I'm sorry for the long delay... I still couldn't check it. I will do my best to check it this weekend, ok?
    Renato Biancalana da Silva
    @ReeSilva
    @fearenales No problems. If I can help (and, of course, if u need) I'll be glad to help
    Felipe Arenales Santos
    @fearenales
    @ReeSilva Is your firewall enabled? That looks like this issue: azukiapp/azk#569 Can you try running the steps described in this issue?
    Renato Biancalana da Silva
    @ReeSilva
    @fearenales works like a charm! \o I'll try to see if I can figure out why the firewall is blocking this and will let u know if I discover something
    Felipe Arenales Santos
    @fearenales
    @ReeSilva By default, your firewall is blocking the port 53 which is used by azk's DNS service. So you have to add an exception rule for accepting connections on it. (https://github.com/azukiapp/azk/issues/569#issuecomment-164294403)
    may you refer this other issue and mark yours as closed, please?
    Renato Biancalana da Silva
    @ReeSilva
    @fearenales But just adding the permission to port 53 on public zone wasn't enough, only works if I shut down firewalld
    Felipe Arenales Santos
    @fearenales
    @ReeSilva that's weird.. can you retrieve from the firewall the blocked ports?
    Slobodan Mišković
    @slobo
    hey folks, do you have a suggestion for the best way to push images built locally using dockerfile: to a remote registry. Say something like azk push systemname
    Slobodan Mišković
    @slobo
    i suppose i could always just adocker build . for the systems I care about, just wondering if anyone is doing something like this and any issues/recommendations
    (i'll admit i'm just now looking into azk deploy to see if it's suitable for pushing stuff to multiple aws instances etc)
    Slobodan Mišković
    @slobo
    in particular, how best to "shrinkwrap" the container together with any needed sourcecode - relating to mount: path() and persistent()
    Danni Friedland
    @BlueHotDog
    Hi guys, i keep getting : Error: HTTP code is 500 which indicates error: server error - Driver aufs failed to remove root filesystem 23bd715d409a1114fac67588ee9de715728af453c1be467538ca4127b2db977e: rename /mnt/sda1/aufs/mnt/23bd715d409a1114fac67588ee9de715728af453c1be467538ca4127b2db977e /mnt/sda1/aufs/mnt/23bd715d409a1114fac67588ee9de715728af453c1be467538ca4127b2db977e-removing: device or resource busy
    Slobodan Mišković
    @slobo
    @BlueHotDog: pretty much exact same thing happened to me the other night, restarting the agent put everything back to normal (azk agent stop; azk agent start)
    Danni Friedland
    @BlueHotDog
    BTW how does azk play with docker for mac?
    seems like the only needed piece is the load-balancer/reverse proxy