azk shellyou access an application's context, and from it you can run what you need.
# Makefile all: azk shell app1 -- mix test azk shell app1 -- gulp test azk shell app1 -- rake test
#!/bin/bash set -e azk shell app1 -- mix test azk shell app1 -- gulp test azk shell app1 -- rake test
azk exec testswhere tests is a command like any other command defined on each system
I'm working with azk v. 0.16.3. When I'm starting/reprovisioning, when it tries to sync, this happens: azk: ⎘ syncing files for `backoffice` system... azk: TypeError: Object #<Object> has no method 'join' azk: at I18n._resolveKey (/i18n-cli:0.0.2/src/index.js:88:60) azk: at I18n.translate (/i18n-cli:0.0.2/src/index.js:44:39) azk: at I18n.t (/i18n-cli:0.0.2/src/index.js:23:28) azk: at Object._status (/azk:0.16.3/src/cli/ui.js:1:14) azk: at Object.fail (/azk:0.16.3/src/cli/ui.js:61:36) azk: at /azk:0.16.3/src/cmds/start.js:103:15 azk: at tryCatcher (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/util.js:24:31) azk: at Promise._settlePromiseFromHandler (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/promise.js:454:31) azk: at Promise._settlePromiseAt (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/promise.js:530:18) azk: at Promise._settlePromises (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/promise.js:646:14) azk: at Async._drainQueue (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/async.js:177:16) azk: at Async._drainQueues (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/async.js:187:10) azk: at Async.drainQueues (/usr/local/Cellar/azk/0.16.3/node_modules/bluebird/js/main/async.js:15:14) azk: at process._tickCallback (node.js:448:13)
What am I missing?
hey folks. we are having issues on Arch linux with
Version : 0.17.0 Docker : 1.10.1 Kernel : 4.4.1 Systemd: 229
We have a 23 systems in this one Azkfile, and while the host system and ulimit don't show anything that indicates we should be running out of resources, we invariably get failures before all systems are up. Messages differ at times (depending on order we try to start systems), but they all have in common that either a thread or process couldn't be started, sometimes "out of memory", sometimes just "resource temporarily unavailable". Nothing in
journalctl shows any clue as to a potential limit or resource we are exhausting.
Tried downgrading kernel back to 4.3, docker to 1.9 and 1.8, and basically the same behaviour.
All this worked about a month or so ago, when systemd was 228. I'm about to try downgrading that too, but was wondering if you guys had any tips or tricks how to debug exactly what is failing.
azk: Error: HTTP code is 500 which indicates error: server error - Driver aufs failed to remove root filesystem 93a1416bcffd4e1e3d6cb00e32b62775a6a4939a4cb46860dcb3a0102fab4e23: rename /mnt/sda1/aufs/mnt/93a1416bcffd4e1e3d6cb00e32b62775a6a4939a4cb46860dcb3a0102fab4e23 /mnt/sda1/aufs/mnt/93a1416bcffd4e1e3d6cb00e32b62775a6a4939a4cb46860dcb3a0102fab4e23-removing: device or resource busy