You can give them more descriptive names and use the -f flag to point to the right path when invoking the docker CLI.
On Thu, Jul 20, 2017 at 7:51 AM Sean Busbey <[email protected]> wrote: > FWIW, I agree this is all confusing. > > > It looks like ./docker/Dockerfile is for Yetus, > > Yep! exactly. > > > ./Dockerfile > > I believe this one is used to provide dependencies needed for running > the dev-support python scripts on builds.a.o. > > I think it's used here: > > https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/ > > > ./hbase_docker/Dockerfile > > This one has a README. It's meant for devs to use to easily get a > standalone instance based on _master_ on their local machine. AFAIK > it's not used in our builds.a.o stuff. > > > ./apache_hbase_topology/Dockerfile is for cluster testing > > This one is part of making it so folks can use clusterdock to deploy > master. AFAIK it's not used in our builds.a.o stuff. I suspect we can > remove it in favor of relying on the one that project publishes: > > https://github.com/clusterdock/topology_apache_hbase > > I think Andrew and Dima were the two I've seen relying on this in the > past for checking RCs, so we should check with them before doing that. > > On Thu, Jul 20, 2017 at 9:22 AM, Mike Drob <[email protected]> wrote: > > Hi Devs, > > > > I noticed that we have 4 Dockerfiles under dev-support. Doing JIRA > > spelunking, I wasn't able to figure out if they are actually duplicative > or > > what the purposes for all of them are. > > > > mdrob@mdrob-MBP:~/IdeaProjects/hbase/dev-support$ find . -name > Dockerfile > > > > ./apache_hbase_topology/Dockerfile > > > > ./docker/Dockerfile > > > > ./Dockerfile > > > > ./hbase_docker/Dockerfile > > > > It looks like ./docker/Dockerfile is for Yetus, > > ./apache_hbase_topology/Dockerfile is for cluster testing, but I can't > > figure out the purpose of the other two. Is there overlap? > > > > > > Thanks, > > > > Mike >
