cli client not included in container about aerospike-server.docker

[volmarl]

We had deliberately removed the tools from the container to create a lighter container. We were planning to create a seperate container for tools. Would a seperate container for tools help you with your test case? Or would you need to have it on the same container?

[cstivers78]

We will release a aerospike-tools container, which you can use to run one of our many tools.

[dnelson]

I don't think any of the existing Docker official-image tests require a secondary container, but maybe @tianon can shed light on whether that is an acceptable way to run the tests.

[fattenap]

+1 aerospike-tools container 👍

[tianon]

Here's one that currently uses separate containers to run the MySQL daemon and the MySQL client: https://github.com/docker-library/official-images/blob/ac172614c20881939886780512eb12ecbf352850/test/tests/mysql-basics/run.sh What I suspect you meant was a separate image, for which the following is a good example: (it builds a second image specifically to get the "cgi-fcgi" client binary) https://github.com/docker-library/official-images/blob/ac172614c20881939886780512eb12ecbf352850/test/tests/php-fpm-hello-web/run.sh

[tclass]

yepp, aerospike-tools container would be great, any update on this?

[volmarl]

We're trying to have it deployed this week.

On Jun 24, 2015, at 9:45 AM, Tobi [email protected] wrote:

yepp, aerospike-tools container would be great, any update on this?

—
Reply to this email directly or view it on GitHub #4 (comment).

[volmarl]

Aerospike Tools container is now deployed:
https://github.com/aerospike/aerospike-tools.docker

[tclass]

@volmarl: wow that was fast, thx :)

P.S. I think you can close the issue now