[
https://issues.apache.org/jira/browse/ATLAS-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109041#comment-17109041
]
Nigel Jones commented on ATLAS-2974:
------------------------------------
Hi [~sonnyhcl] . I'm not actively working on any atlas specific work right now,
but we do build atlas images in our Egeria project. We have a helm chart (for
k8s) that sets up an environment to test/demo/develop interop between Egeria
and atlas
That image build can be found at
[https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment/docker/build-images/apache/atlas]
. That is building Atlas 2.0 rather than master. We used to build, but since
we've not done anything atlas related for a while the build got dropped when we
moved infrastructure. The last build is from 8 months ago at
[https://hub.docker.com/repository/docker/odpi/apache-atlas?ref=login] . I do
built it manually occasionally, and we are moving it's repo in the next few
weeks so I may revisit it then.
We use this as a base image, then also build
[https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-deployment/docker/apache-atlas/Dockerfile]
for a few specific configuration steps. This is part of our build pipelines at
[https://dev.azure.com/ODPi/Egeria/_build?definitionId=13&_a=summary]
Hope that background helps.
But for your specific question on port 2181 - that's zookeeper – I haven't run
a 'normal' atlas build for well over a year, and I can't remember that aspect
of setup sorry, but we do slightly modify the normal atlas config for kafka
(which uses zookeeper) in the second image - so we don't clash with the
zookeeper/kafka configuration we use with our code. So I would look at whether
zookeeper is starting up correctly, and which port it is using.
You could also try the image above to see if it works - I've not tested
recently. I'll take a quick look to see if it works if I get a chance in the
next few days.
> Docker build: Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin...
> --------------------------------------------------------------------------------------
>
> Key: ATLAS-2974
> URL: https://issues.apache.org/jira/browse/ATLAS-2974
> Project: Atlas
> Issue Type: Bug
> Reporter: Dmitry Goryunov
> Assignee: Xinran Tinney
> Priority: Major
> Attachments: tmp
>
>
> Version: commit 945de013f5466ffcf71d16c6ec1772fdee83e2f6 (Also reproducable
> with 1.1.0-rc2)
>
> Runnign command:
> {code:java}
> docker build -t atlas_docker .
> {code}
> Breaks at some point with:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (enforce-versions) on project apache-atlas: Some Enforcer rules have failed.
> Look above for specific messages explaining why the rule failed. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :apache-atlas
> The command '/bin/sh -c mvn clean install -DskipTests
> -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1
> {code}
> The complete logs are attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
