phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francis Chuang <>
Subject Re: [DISCUSS] Docker images for Phoenix
Date Mon, 25 Jun 2018 23:13:30 GMT
I think it would make things easier if we reduce the scope of the docker 
images to just an all-in-one HBase + Phoenix + all Phoenix features 
enabled testing image to simplify things for now.

Since Phoenix has tags for $HBASE_VER:$PHOENIX_VER for each release, we 
should be able to use build hooks (see

We simply write a shell script to parse the tag, split it into its 
constituent parts and pass it to the docker build command as BUILD_ARGS. 
The docker file would then reference these build args and build an image 
for each tag.


On 26/06/2018 3:52 AM, Josh Elser wrote:
> Moving this over to the dev list since this is a thing for developers 
> to make the call on. Would ask users who have interest to comment over 
> there as well :)
> I think having a "one-button" Phoenix environment is a big win, 
> especially for folks who want to do one-off testing with a specific 
> version.
> My biggest hesitation (as you probably know) is integration with the 
> rest of Apache infrastructure. That's a problem we can work on solving 
> though (I think, just automation around publishing).
> On 6/21/18 9:24 PM, Francis Chuang wrote:
>> Hi all,
>> I currently maintain a HBase + Phoenix all-in-one docker image[1]. 
>> The image is currently used to test Phoenix support for the Avatica 
>> Go SQL driver[2]. Judging by the number of pulls on docker hub 
>> (10k+), there are probably other people using it.
>> The image spins up HBase server with local storage, using the bundled 
>> Zookeeper with Phoenix support. The Phoenix query server is also 
>> started on port 8765.
>> While the image is definitely not suitable for production use, I 
>> think the test image still has valid use-cases and offers a lot of 
>> convenience. It's also possible to update the image in the future so 
>> that it can be used to spin up production clusters as well as testing 
>> instances (similar to what Ceph has done[3]).
>> Would the Phoenix community interested in accepting the dockerfile + 
>> related files and making it part of Phoenix? The added benefit of 
>> this is that it would be possible to configure some automation and 
>> have the docker images published directly to dockerhub as an 
>> automated build for each release.
>> Francis
>> [1]
>> [2]
>> [3]

View raw message