Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Danni Friedland
    @BlueHotDog
    i'm experiencing a weird issue with azk+nodejs
    if i do a full rebuild of all my services(about 10) it usually fails(and shutsdown them as well)
    but if i run them 1 by 1, everything goes well(usually)
    Bartek Kus
    @bartekus
    probably your wait time is too short and the whole things timesout
    maybe try like: wait: {"retry": 2, "timeout": 50000},
    Danni Friedland
    @BlueHotDog
    tried.. the actual build fails on npm install
    npm + docker is fragile in my experience
    my question is, how can i run the start/restart --rebuild one by one
    my shell powers are weak
    Bartek Kus
    @bartekus
    you can do azk start <systemName> individualy, and also azk shell <systemName> — npm run <npmScriptName> //or any other cmd line command
    Danni Friedland
    @BlueHotDog
    yeah, but if i've 10 systems it's quite a labor
    Danni Friedland
    @BlueHotDog
    azk status --text | tr -s ' ' | cut -d ' ' -f 2 | tail -n+2 | azk start $1
    is the trick
    Marcus Gadbem
    @marcusgadbem
    Cool :) I was just trying to accomplish that using grep
    Danni Friedland
    @BlueHotDog
    :)
    Felipe Arenales Santos
    @fearenales
    @BlueHotDog that's odd.. It shouldn't be an issue to start all systems with an azk start.
    May I take a look in your Azkfile?
    Slobodan Mišković
    @slobo
    @fearenales: just had a chance to reboot the entire machine, but no luck. To clarify, i'm referring to stuff like inotify in the containers noticing the change on the host os files mounted with path(). Or is this one of the issues with VBOXSF?
    another question I have is if there is a way to control the size of swapfile created inside the VM - I set AZK_VM_MEMORY=8192, which then created a 12G file, stealing useful room in the vm disk. I tried manually trimming the file, but on next azk start it recreated 12G swapfile. I prefer to actually have no swap in azk agent vm, since I give it enough memory and it never swaps, but I'd be happy with at least lowering it down to 1G or similar
    Slobodan Mišković
    @slobo
    ok, i see here https://github.com/azukiapp/debian2docker/blob/azk_iso/includes.chroot/lib/live/config/0361-swap#L10 it can be configured via VBox guest property, but guest gets recreated every time agent starts, right? So it would need to be added somewhere in azk, like perhaps server.js:installVMcould vm.setProperty()?
    Slobodan Mišković
    @slobo
    ok, I gave it a go, let me know what you think: #642
    Andreas Schmelas
    @m9dfukc
    Hey folks, I'm having issues with the sync() mount option. I'm experiencing slowness with my php application on OsX, so I switched from using the path() to sync() unfortunately it looks like if no files at all are now available to the VM.

    I switched from

    mounts: { '/azk/#{manifest.dir}/node_modules': persistent('node_modules'), '/azk/#{manifest.dir}/vendor': persistent('vendor'), '/azk/#{manifest.dir}': path('.') }

    to

    mounts: { '/azk/#{manifest.dir}/node_modules': persistent('node_modules'), '/azk/#{manifest.dir}/vendor': persistent('vendor'), '/azk/#{manifest.dir}': sync('.', {'shell': true}) }

    but now it seems that the files won't get synced at all :(

    Any help would be much appreciated. Thanks
    Andreas Schmelas
    @m9dfukc
    By the way, running 'azk 0.17.0' on OsX 10.11
    Vytenis
    @FDiskas
    $ azk agent start
    displays an error
    azk: Error: HTTP code is 500 which indicates error: server error - failed to create endpoint dev.azk.io_type.daemon_mid.ce833fc9c9_sys.dns_seq.1_uid.f4f2aae0e4 on network bridge: Bind for 172.17.0.1:53 failed: port is already allocated
    
    azk:     at /usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
    azk:     at getCause (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
    azk:     at [object Object].Modem.buildPayload (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
    azk:     at IncomingMessage.<anonymous> (/usr/lib/azk/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
    azk:     at IncomingMessage.emit (events.js:117:20)
    azk:     at _stream_readable.js:944:16
    azk:     at process._tickCallback (node.js:448:13)
    Vytenis
    @FDiskas
    $ azk agent start --log=debug --no-daemon
    Results I will post in next message
    Vytenis
    @FDiskas
    netstat -tulpn | grep :53
    tcp        0      0 192.168.124.1:53        0.0.0.0:*               LISTEN      -                   
    udp        0      0 172.17.0.1:53           0.0.0.0:*                           -                   
    udp        0      0 192.168.124.1:53        0.0.0.0:*                           -                   
    udp6       0      0 :::5353                 :::*                                -
    docker ps
    CONTAINER ID        IMAGE                COMMAND                  CREATED             STATUS              PORTS                   NAMES
    f726b39d94a7        tonistiigi/dnsdock   "/go/bin/dnsdock -nam"   4 days ago          Up 3 days           172.17.0.1:53->53/udp   dnsdock
    docker stop f726b39d94a7
    And then everything is working now
    Sorry for the flood
    Vytenis
    @FDiskas
    This message was deleted
    This message was deleted
    Is it posible to change the default development domain from azk.io to something else?
    Vytenis
    @FDiskas
    All files created in the container are with wrong permissions. In host I cant delete or modify them. My user has a docker group
    Vytenis
    @FDiskas
    if Try to run
    azk restart -R
    I hope that it will restart and reprovision. I know that prossion commands is running slow, like npm install and composer install, bu I got very quick response with success.
    Saito
    @saitodisse
    Hi @FDiskas. Try to run azk restart -Rvv to enable a verbose output.
    :point_up: March 7, 2016 9:34 AM Yep, Docker always create files with root owner
    All files created in the container are with wrong permissions. In host I cant delete or modify them. My user has a docker group
    you can run this to get your files back: sudo chown -Rid -un:id -gn./PROJECT_FOLDER/
    Saito
    @saitodisse

    @m9dfukc

    mounts: {
     '/azk/#{manifest.dir}/node_modules': persistent('node_modules'),
     '/azk/#{manifest.dir}/vendor': persistent('vendor'),
     '/azk/#{manifest.dir}': sync('.', {'shell': true}) 
    }

    sync Note it's a one-way sync, so you still have to add entries in mounts indicating which folders need to use the share option (using path or persistent).

    Vytenis
    @FDiskas
    sudo chown -R $USER:$USER .
    this hellped to get access to the files
    Saito
    @saitodisse
    Thats right. You can create a shell script to do that all time you need. Maybe soon Docker will fix this.
    Vytenis
    @FDiskas
    I got working this. In docker-compose I have no problems with permmissions
    Saito
    @saitodisse
    @FDiskas even when you get files outside the container?
    Vytenis
    @FDiskas

    I'm accessing the shell

    docker exec -u 1000 -it $CONTAINER bash

    in Docker file

    RUN usermod -u 1000 www-data
    RUN chown 1000:1000 /var/www
    Saito
    @saitodisse
    Interesting. Thanks for the adivice
    Saito
    @saitodisse
    @m9dfukc, maybe your problem on sync is related to .gitignore - you may check this: http://docs.azk.io/en/reference/azkfilejs/mounts.html#excluded-folders
    Andreas Schmelas
    @m9dfukc
    @saitodisse ... thanks, just checked that – still doesn't work :(
    I fear I'm missing something essential here?! "One-way sync" means it's syncing my local files into the VM - right?!