Hi all, Whether or not we release the RC1, we have to resolve the issues ASAP. I have submitted a PR https://github.com/apache/druid/pull/11299 , and I'm still testing these changes on different platforms(macOS and centos). But since the reported problems are platform-related, any help to verify that change is appreciated.
Thanks. frank chen <frankc...@apache.org> 于2021年5月25日周二 下午6:47写道: > > Do we see Unable to use AWS Fargate bind mounts with Dockerfile · Issue > #11278 · apache/druid (github.com) > <https://github.com/apache/druid/issues/11278> as a regression test > failure for https://github.com/apache/druid/pull/11167 > > > Furkan KAMACI <furkankam...@gmail.com> 于2021年5月25日周二 下午3:31写道: > >> Hi, >> >> Here is my opinion: >> >> Druid has had problems with docker for a while now. We use Druid on a >> dockerized environment and manually solve this problem via setting >> permissions. It is not a blocker issue, and we can release the artifact. >> >> However, this is a bugfix release that aims to cover Docker volume issues >> (whether directly related to the discussed problem or not); we should >> solve >> this problem and then start a new RC spin. Otherwise, it seems that this >> conversation will take more days to finalize (it has been 11 days since >> the >> vote thread has started), and we will not be able to release it soon. >> Solving that issue may result in faster release. >> >> So, I am -0. >> >> Kind Regards, >> Furkan KAMACI >> >> On Tue, May 25, 2021 at 10:06 AM Clint Wylie <cwy...@apache.org> wrote: >> >> > I agree that this probably isn't a blocker, but also agree based on the >> > number of reports that we should consider either fixing so that the >> > docker-compose quickstart instructions work as is, or adjust the docs so >> > that the instructions at least include something about setting the >> > permissions so that things can work correctly. Given that I still don't >> > have enough PMC votes yet to release 0.21.1, and I don't really have a >> > strong preference of which thing we do (nor am quite sure on what the >> > correct docker fix is), anyone have opinions on the best path forward? >> > >> > On Sat, May 22, 2021 at 3:56 PM Jihoon Son <jihoon...@apache.org> >> wrote: >> > >> > > Xavier, that's good to know! Glad we already have some. >> > > >> > > On Fri, May 21, 2021 at 8:41 AM Xavier Léauté >> > > <xav...@confluent.io.invalid> wrote: >> > > > >> > > > > I agree with you that the root cause is lack of some automated >> tests >> > > > > against released docker images. >> > > > > >> > > > >> > > > Since https://github.com/apache/druid/pull/11187 we are now running >> > k8s >> > > > integration tests against the same image we release. >> > > > So this should at least catch the kind of issues people would >> encounter >> > > > with a typical k8s deployment. >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org >> > > For additional commands, e-mail: dev-h...@druid.apache.org >> > > >> > > >> > >> >