Hi Clint, According to the docker instruction `COPY --chown=druid:druid --from=builder /opt /opt` in docker file, the user `druid` has permission to create directories under /opt.
I don't know what happened. I will check RC1 tomorrow on a fresh linux environment to see if there's such problem. Clint Wylie <cwy...@apache.org> 于2021年5月19日周三 上午6:23写道： > Hmm, I'm actually still seeing a permissions related issue with the rc1 > Docker image and Linux (Docker on Mac OS seems to work ok, which is where I > initially tested). > > middlemanager | 2021-05-18T21:20:39,239 INFO [forking-task-runner-0] > org.apache.druid.indexing.overlord.ForkingTaskRunner - Exception caught > during execution > middlemanager | org.apache.druid.java.util.common.IOE: Unable to create > task log dir[/opt/data/indexing-logs] > middlemanager | at > > org.apache.druid.indexing.common.tasklogs.FileTaskLogs.pushTaskLog(FileTaskLogs.java:59) > ~[druid-indexing-service-0.21.1.jar:0.21.1] > middlemanager | at > > org.apache.druid.indexing.overlord.ForkingTaskRunner$1.call(ForkingTaskRunner.java:386) > [druid-indexing-service-0.21.1.jar:0.21.1] > middlemanager | at > > org.apache.druid.indexing.overlord.ForkingTaskRunner$1.call(ForkingTaskRunner.java:137) > [druid-indexing-service-0.21.1.jar:0.21.1] > middlemanager | at > java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_275] > middlemanager | at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:1.8.0_275] > middlemanager | at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:1.8.0_275] > middlemanager | at java.lang.Thread.run(Thread.java:748) > [?:1.8.0_275] > middlemanager | 2021-05-18T21:20:39,247 INFO [forking-task-runner-0] > org.apache.druid.indexing.overlord.ForkingTaskRunner - Removing task > directory: > var/druid/task/index_parallel_wikipedia_gmkopeph_2021-05-18T21:20:10.899Z > > the 'storage' directory that is used for tasklogs and deep storage in the > docker-compose file seems to belong to root. If I change ownership to the > user it works. > > I am unsure if this is necessarily a blocker because the containers > themselves do seem to actually work ok, and this seems to be an issue with > the locally attached volume deep storage used by the example compose file > (which I also forgot to update the version to 0.21.1 in this release). > Presumably everything would work ok if using something like s3 for deep > storage, though I haven't had the chance to confirm this yet. > > > On Fri, May 14, 2021 at 12:42 PM Clint Wylie <cwy...@apache.org> wrote: > > > Hi all, > > > > I have created a build for Apache Druid 0.21.1, release > > candidate 1. > > > > Thanks to everyone who has helped contribute to the release! You can read > > the proposed release notes here: > > https://github.com/apache/druid/issues/11249 > > > > The release candidate has been tagged in GitHub as > > druid-0.21.1-rc3 (9d142a2f19cceef38173e8d463a8cc1dfe1cb7ec), > > available here: > > https://github.com/apache/druid/releases/tag/druid-0.21.1-rc1 > > > > The artifacts to be voted on are located here: > > https://dist.apache.org/repos/dist/dev/druid/0.21.1-rc1/ > > > > A staged Maven repository is available for review at: > > https://repository.apache.org/content/repositories/orgapachedruid-1024/ > > > > Staged druid.apache.org website documentation is available here: > > https://druid.staged.apache.org/docs/0.21.1/design/index.html > > > > A Docker image containing the binary of the release candidate can be > > retrieved via: > > docker pull apache/druid:0.21.1-rc1 > > > > artifact checksums > > src: > > > > > 8ac8267e9fa8aebbd7e2aa7bf30cfa598083eea4e862856f2e28521443a74c8b4f3d7ede5ba9837ee802028913995567d8f10e991f2aac069fea0155b30083f9 > > bin: > > > > > 170a8861c2bd00078689316013b32d16e110c021be87bf183898b4eb3ffc1c06ca56e3c7b92ca38f9732ba3cf4ff4c1de22a68d7a4b93e6dc271b3c994416053 > > docker: 16b47d4d03b41aa6c5784b6f356d51bb7d3c50198cb5f8a289d0e9c4d425bb26 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/cwylie.asc > > > > This key and the key of other committers can also be found in the > project's > > KEYS file here: > > https://dist.apache.org/repos/dist/release/druid/KEYS > > > > (If you are a committer, please feel free to add your own key to that > file > > by following the instructions in the file's header.) > > > > > > Verify checksums: > > diff <(shasum -a512 apache-druid-0.21.1-src.tar.gz | \ > > cut -d ' ' -f1) \ > > <(cat apache-druid-0.21.1-src.tar.gz.sha512 ; echo) > > > > diff <(shasum -a512 apache-druid-0.21.1-bin.tar.gz | \ > > cut -d ' ' -f1) \ > > <(cat apache-druid-0.21.1-bin.tar.gz.sha512 ; echo) > > > > Verify signatures: > > gpg --verify apache-druid-0.21.1-src.tar.gz.asc \ > > apache-druid-0.21.1-src.tar.gz > > > > gpg --verify apache-druid-0.21.1-bin.tar.gz.asc \ > > apache-druid-0.21.1-bin.tar.gz > > > > Please review the proposed artifacts and vote. Note that Apache has > > specific requirements that must be met before +1 binding votes can be > cast > > by PMC members. Please refer to the policy at > > http://www.apache.org/legal/release-policy.html#policy for more details. > > > > As part of the validation process, the release artifacts can be generated > > from source by running: > > mvn clean install -Papache-release,dist -Dgpg.skip > > > > The RAT license check can be run from source by: > > mvn apache-rat:check -Prat > > > > This vote will be open for at least 72 hours. The vote will pass if a > > majority of at least three +1 PMC votes are cast. > > > > [ ] +1 Release this package as Apache Druid 0.21.1 > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > [ ] -1 Do not release this package because... > > > > Thanks! > > >
