"Automated installation and configuration of development environments" - for pt-BR support, please check out https://gitter.im/azukiapp/azk/pt
seems docker for osx and windows is publicly released: https://blog.docker.com/2016/07/docker-for-mac-and-windows-production-ready/
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
azk: Error: 404: >> url: https://registry-1.docker.io/v1/repositories/library/rabbitmq/tags/3.6.5-management
@gullitmiranda
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
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.02elapsedvs 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
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
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
seems on resize we were trying to get width of
stderr instead of stdout
(this could be a bug with node?)
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?
talking about this line here https://github.com/azukiapp/azk/blob/ca00f3851752cc6be6fcbac33a08976f5f7eb808/src/system/run.js#L96
quick test without
yield seems to cause no ill sideeffects and speeds up our staging scripts that do a series of azk shell commands one after another
Guys, I have a question. I run AZK on my user with the "azk start" command, so he calls docker and instantiates the container. The problem is that the created files and folders created by the container are allowed root in my local folder. Because docker runs as root. How to solve it?
Hi @chiaretto, you can create a docker group and user to run docker without root if you use
sudo usermod -aG docker $(id -un) See more here: http://docs.azk.io/en/installation/linux.html
@annielmenezes actually @chiaretto is right, because the user that runs inside the container is the root user, even if you're not running Docker as root.
This is a known issue from Docker and the current solution (workaround, actually) is: after exiting the container, fix the generated files/folders permissions running the following command from inside your project's folder:
This is a known issue from Docker and the current solution (workaround, actually) is: after exiting the container, fix the generated files/folders permissions running the following command from inside your project's folder:
sudo chown -R `id -un`:`id -gn` .
hey folks, we get intermittent "No internet Connection" on our build server. I see here that azk checks for network connection before attempting pull https://github.com/azukiapp/azk/blob/667cd76247dfa21c1c79344aeeed32aa4f116317/src/images/index.js#L74
And it seems
connectivity npm package is used, which in that version tries to connect to google.com:80. I don't understand why this check is needed?
What is the problem with letting image pull discover itself whether it can reach docker repo or not?
How can I fix this?