[
https://issues.apache.org/jira/browse/ATLAS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125800#comment-16125800
]
Nigel Jones commented on ATLAS-2012:
------------------------------------
Hi Richard,
Thanks for posting that patch. I gave it a go under WIndows 10 x64 (with
docker installed!) and the build fell over at :
Step 6/21 : RUN mkdir -p /usr/java
---> Running in b9952e21fdd7
---> 5b1b164a474c
Removing intermediate container b9952e21fdd7
Step 7/21 : RUN tar xzf *jdk* --strip-components 1 -C /usr/java
---> Running in 98080c6e748e
tar (child): *jdk*: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
The command '/bin/sh -c tar xzf *jdk* --strip-components 1 -C /usr/java'
returned a non-zero code: 2
C:\src\atlas\dev-support\atlas-docker>dir
Volume in drive C is Windows
Volume Serial Number is CE3F-3B05
Directory of C:\src\atlas\dev-support\atlas-docker
14/08/2017 13:56 <DIR> .
14/08/2017 13:56 <DIR> ..
14/08/2017 13:55 8,534,562 apache-maven-3.5.0-bin (1).tar.gz
14/08/2017 13:51 2,208 Dockerfile
14/08/2017 13:55 207,382,584 jdk-8u144-windows-x64 (1).exe
14/08/2017 13:51 2,857 README.md
4 File(s) 215,922,211 bytes
2 Dir(s) 31,488,966,656 bytes free
Just taking a look now, but I also had another thought -- "openjdk" could be a
better option to use instead of oracle java (pretty much the same anyway), and
has the benefit of being installing via apt. Similarly maven3 is available at
3.3.9 - at least with Ubuntu 16.10
I updated the patch to install jdk/maven via APT, and my build progressed well
and completed just fine. I was able to login to the Atlas UI. I did get the
hbase shell though didn't need it. Attaching my modified patch
> Docker - image & hub - for Atlas
> --------------------------------
>
> Key: ATLAS-2012
> URL: https://issues.apache.org/jira/browse/ATLAS-2012
> Project: Atlas
> Issue Type: New Feature
> Reporter: Nigel Jones
> Assignee: Péter Gergő Barna
> Attachments: atlas_docker.patch
>
>
> Docker is increasingly become a standard way of easily running components in
> a flexible manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's
> appeal
> 1. We could provide a simple example of how to create a docker image from the
> Atlas build. This could be published on the wiki & it would make it easier
> for developers to use Atlas within a docker environment - mostly by
> addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build
> process. This builds on #1 by automating the creation of the image & making
> it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub,
> making it near trivial for any developer to easily pull down and experiment
> with Atlas. Full source of course would be provided/documented so that a user
> could customize as needed for their environment plus of course improve what
> is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts
> in other teams to easily work together & be orchestrated
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
