Closed dnelson closed 6 years ago
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?
We will release a aerospike-tools container, which you can use to run one of our many tools.
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.
+1 aerospike-tools container :+1:
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
yepp, aerospike-tools container would be great, any update on this?
We're trying to have it deployed this week.
On Jun 24, 2015, at 9:45 AM, Tobi notifications@github.com wrote:
yepp, aerospike-tools container would be great, any update on this?
— Reply to this email directly or view it on GitHub https://github.com/aerospike/aerospike-server.docker/issues/4#issuecomment-114938611.
Aerospike Tools container is now deployed: https://github.com/aerospike/aerospike-tools.docker
@volmarl: wow that was fast, thx :)
P.S. I think you can close the issue now
I was trying to write basic functionality tests for https://github.com/docker-library/official-images/issues/586 but was unable to access the database via the docker container because the tools that are mentioned in the documentation does not appear to be included in the Docker container.
Can the cli client be added to the container?