sburn/docker-apache-atlas

This Apache Atlas is built from the latest release source tarball and patched to be run in a Docker container.

Apache Atlas Docker image

This Apache Atlas is built from the 2.3.0-release source tarball and patched to be run in a Docker container.

Atlas is built with embedded HBase + Solr and it is pre-initialized, so you can use it right after image download without additional steps.

If you want to use external Atlas backends, set them up according to the documentation.

N.B. The image many not currently launch correctly if run in Docker rootless mode

Basic usage

1. Start Apache Atlas in a container exposing Web-UI port 21000:

docker run -d \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas

Please, take into account that the first startup of Atlas may take up to few mins depending on host machine performance before web-interface become available at http://localhost:21000/

Web-UI default credentials: admin / admin

Usage options

Gracefully stop Atlas:

docker exec -ti atlas /apache-atlas/bin/atlas_stop.py

Check Atlas startup script output:

docker logs atlas

Check Atlas application.log (useful at the first run and for debugging during workload):

docker exec -ti atlas tail -f /apache-atlas/logs/application.log

Run the example (this will add sample types and instances along with traits):

docker exec -ti atlas /apache-atlas/bin/quick_start.py

Start Atlas overriding settings by environment variables (to support large number of metadata objects for example):

docker run --detach \
    -e "ATLAS_SERVER_OPTS=-server -XX:SoftRefLRUPolicyMSPerMB=0 \
    -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC \
    -XX:+CMSParallelRemarkEnabled -XX:+PrintTenuringDistribution \
    -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=dumps/atlas_server.hprof \
    -Xloggc:logs/gc-worker.log -verbose:gc -XX:+UseGCLogFileRotation \
    -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1m -XX:+PrintGCDetails \
    -XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps" \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas

Explore logs: start Atlas exposing logs directory on the host

docker run --detach \
    -v ${PWD}/atlas-logs:/apache-atlas/logs \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas

Custom configuration: start Atlas exposing conf directory on the host

docker run --detach \
    -v ${PWD}/pre-conf:/apache-atlas/conf \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas

Data persistency: start Atlas with data directory mounted on the host

docker run --detach \
    -v ${PWD}/data:/apache-atlas/data \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas

Tinkerpop Gremlin support

Image contains build-in extras for those who want to play with Janusgraph, and Atlas artifacts using Apache Tinkerpop Gremlin Console (gremlin CLI).

1. You need Atlas container up and running as shown above.

2. Install gremlin-server and gremlin-console into the container by running included automation script:

docker exec -ti atlas /gremlin/install-gremlin.sh

3. Start gremlin-server in the same container:

docker exec -d atlas /gremlin/start-gremlin-server.sh

4. Finally, run gremlin-console interactively:

docker exec -ti atlas /gremlin/run-gremlin-console.sh

Gremlin-console usage example:

         \,,,/
         (o o)
-----oOOo-(3)-oOOo-----

gremlin>:remote connect tinkerpop.server conf/remote.yaml session
==>Configured localhost/127.0.0.1:8182-[d1b2d9de-da1f-471f-be14-34d8ea769ae8]
gremlin> :remote console
==>All scripts will now be sent to Gremlin Server - [localhost/127.0.0.1:8182]-[d1b2d9de-da1f-471f-be14-34d8ea769ae8] - type ':remote console' to return to local mode
gremlin> g = graph.traversal()
==>graphtraversalsource[standardjanusgraph[hbase:[localhost]], standard]
gremlin> g.V().has('__typeName','hdfs_path').count()

Environment Variables

The following environment variables are available for configuration:

Name	Default	Description
JAVA_HOME	/usr/lib/jvm/java-8-openjdk-amd64	The java implementation to use. If JAVA_HOME is not found we expect java and jar to be in path
ATLAS_OPTS		any additional java opts you want to set. This will apply to both client and server operations
ATLAS_CLIENT_OPTS		any additional java opts that you want to set for client only
ATLAS_CLIENT_HEAP		java heap size we want to set for the client. Default is 1024MB
ATLAS_SERVER_OPTS		any additional opts you want to set for atlas service.
ATLAS_SERVER_HEAP		java heap size we want to set for the atlas server. Default is 1024MB
ATLAS_HOME_DIR		What is is considered as atlas home dir. Default is the base location of the installed software
ATLAS_LOG_DIR		Where log files are stored. Defatult is logs directory under the base install location
ATLAS_PID_DIR		Where pid files are stored. Defatult is logs directory under the base install location
ATLAS_EXPANDED_WEBAPP_DIR		Where do you want to expand the war file. By Default it is in /server/webapp dir under the base install dir.

For additional infomation about configurable options check official Apache Atlas documentation.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there to see if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.

Maintainer

This image is maintained by Vadim Korchagin

• https://github.com/sburn/docker-apache-atlas

docker-apache-atlas's Issues

Non-Root user

Are you able to ensure this runs as a non-root user (e.g. 'atlas') so that it can be deployed to services such as Openshift?

Thanks

PAtch https://github.com/apache/atlas/pull/20.patch not found

In Dockerfile
https://github.com/sburn/docker-apache-atlas/blob/master/Dockerfile
used patch and
This patch is absent at this path. Where I can found this patch?

atlas version 2.1

Hello,

Can we get image for latest version of atlas release some days back.

Thanks

Error "No such file or directory" when starting Atlas with configuration volumes exposed

Hi!

One example from docs:

docker run --detach \
    -v ${PWD}/pre-conf:/opt/apache-atlas-2.1.0/conf \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas \
    /opt/apache-atlas-2.1.0/bin/atlas_start.py

Is not working due to:

Exception: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties'
Traceback (most recent call last):
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 191, in <module>
    returncode = main()
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 84, in main
    is_hbase = mc.is_hbase(confdir)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 411, in is_hbase
    storageBackEnd = getConfig(confFile, STORAGE_BACKEND_CONF)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 689, in getConfig
    for line in open(file).readlines():
IOError: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties'

But if you run the container without configs exposed - file atlas-application.properties could be found in /opt/apache-atlas-2.1.0/conf. Not sure why it's happening.

Typo for quick start script in Readme

The Readme currently reads:

Run the example (this will add sample types and instances along with traits):
docker exec -ti atlas /opt/apache-atlas-2.1.0/bin/quick-start.sh

It should read:

Run the example (this will add sample types and instances along with traits):
docker exec -ti atlas /opt/apache-atlas-2.1.0/bin/quick_start.py

ie. the script is now named quick_start.py and not quick-start.sh.

Many thanks for this great job!

Openshift start error, conf not found

Once deployed in Openshift it won't run. The error is quite straightforward, but I have no idea why the file is not in place.
Thanks for any hint.

Exception: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties' 

Traceback (most recent call last):
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 191, in <module>
    returncode = main()
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 84, in main
    is_hbase = mc.is_hbase(confdir)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 411, in is_hbase
    storageBackEnd = getConfig(confFile, STORAGE_BACKEND_CONF)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 689, in getConfig
    for line in open(file).readlines():
IOError: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties'

Thank you for this repo!

I just wanted to say thank you for creating this docker image and sharing this repo. I've been trying to setup a docker image myself and ran into numerous complications. It was simple to pull the docker image and follow your quick start instructions.

Thank you for making my job and my life easier :). Kudos to you.

Kurt

atlas 2.1.0 - 503 error

Hi ,

            I have installed the Atlas(apache-atlas-sources-2.1.0) After all the setup

have been done, we ran the atlas-start.py and the atlas is running on port
21000.When we are accessing the atlas, we are facing 503 Service Unavailable
Error.

We checked the logs from application.log file. We got below issue

2020-12-13 06:29:02,309 WARN - [main:] ~ JMX is not enabled to receive
remote connections. Please see cassandra-env.sh for more info.
(CassandraDaemon:81)

2020-12-13 06:29:02,310 ERROR - [main:] ~ cassandra.jmx.local.port missing
from cassandra-env.sh, unable to start local JMX service.null
(CassandraDaemon:87)

We see there is no "cassandra-env.sh" file in atlas and we
tried other ways and didn't find any solution for the above error.

Could you please help us in rectify these problem so that it
will be very helpful to us.

Creating docker image takes a lot of time

Hi, while I tried building my own docker image, the build takes a lot of time. Any solution on how to speed up the build process?

mvn clean -Dmaven.repo.local=/tmp/.mvn-repo -DskipTests package -Pdist,embedded-hbase-solr

This command is the culprit I believe.

Also my internet is not an issue as it is fast.

how to exec import-hive.sh

i could not find import-hive.sh

Unable to Start: ConnectException: Connection refused then stuck at REST_API_ENABLE_TYPE+OVERRIDE

Hi, I'm trying to get the container running and the startup seems stuck at the application.log message REST_API_DELETE_TYPE_OVERRIDE=false (AuditFilter:69). The only other thing strange I see in the log is a line that read sendThread(...) ~ Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect (ClientCnxn$SendThread:1102) java.net.ConnectException: Connection refused. The server never gets past starting and the UI does not load. Any ideas?

Data Persistence

Is there a way to persist data even after the container is removed and then re-deployed. I am able to successfully mount the data directory from your instructions and the data persists when I stop and start the container, but when I remove and re-deploy the container the existing entities do not appear in the Atlas UI.

Http 503 Service Unavailable Error when connecting from Java Client

Not sure if it's an issue with the image as the Admin Dashboard works fine. But I cannot connect via the Atlas Java client and get a 503 error.

Documentation link broken

When you wrote about setting up external Atlas backends, the documentation link you referenced in your main README is broken.

Mounting conf directory does not work on Windows nor on Linux

Hello and many thanks for this great docker image.
The readme proposes the following command start Atlas exposing conf directory on the host to place and edit configuration files directly:

docker run --detach \
    -v ${PWD}/pre-conf:/opt/apache-atlas-2.1.0/conf \
    -p 21000:21000 \
    --name atlas \
    sburn/apache-atlas \
    /opt/apache-atlas-2.1.0/bin/atlas_start.py

But this doesn't work on Windows nor on Linux. On both systems, I get the following error:

Exception: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties' 
Traceback (most recent call last):
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 191, in <module>
    returncode = main()
  File "/opt/apache-atlas-2.1.0/bin/atlas_start.py", line 84, in main
    is_hbase = mc.is_hbase(confdir)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 411, in is_hbase
    storageBackEnd = getConfig(confFile, STORAGE_BACKEND_CONF)
  File "/opt/apache-atlas-2.1.0/bin/atlas_config.py", line 689, in getConfig
    for line in open(file).readlines():
IOError: [Errno 2] No such file or directory: '/opt/apache-atlas-2.1.0/conf/atlas-application.properties'

As a temporary workaround, I access bash from the container with docker exec -t -i atlas /bin/bash, then apt-get install nano and edit the configuration file with nano. But it would be very handy to be able to mount the configuration on the host file system.

### Is there an existing issue for this?

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

I have written an npm initializer @usr/create-foo and installed it globally with npm install -g but not published.

I then attempt to use this initializer with npm init @usr/foo but this fails after attempting to find the package in the registry, where it doesn't exist because it hasn't been published.

npm init @usr/foo is translated to npm exec @usr/create-foo as described in the docs. But this fails to find the bin from the globally installed package.

package.json of the initializer includes:

{
  "name": "@usr/create-foo",
  "bin": "index.js"
...
}

Documentation for package.json includes: If you have a single executable, and its name should be the name of the package, then you can just supply it as a string.

Here, the package name is @usr/create-foo so the name of the executable should be @usr/create-foo and this is consistent with the executable that npm exec @usr/create-foo attempts to execute.

The problem is that npm install -g . in the directory of the initializer package doesn't install an executable @usr/create-foo as the documentation indicates it should. Rather, it installs create-foo. Therefore, npm exec @usr/create-foo can't find the executable: it hasn't been installed as such but rather with the different name create-foo.

The problem is compounded by the fact that npm exec @usr/create-foo looks for a locally installed package but it doesn't look for a globally installed package. It goes straight to trying to download the package, ignoring the globally installed package.

I hacked libnpmexec/lib/index.js to look for the globally installed package. It gets the manifest OK and derives the name of the executable: create-foo rather than @usr/create-foo. But still it doesn't work because next it checks that every package in the manifest list (there is only one) is installed locally - again ignoring the globally installed package.

A bit more hacking and I could have it working.

I can simply ignore the 'sugar' of npm init @usr/foo and run the bin directly: create-foo works fine although @usr/create-foo does not, despite the documentation for package.json.

Rather than bin being set to a string value in package.json I also tried:

{
  "name": "@usr/create-foo",
  "bin": {
    "@usr/create-foo": "index.js"
  },
  ...
}

But even with the executable name given explicitly rather than implied by the package name, npm install -g installs the executable as create-foo rather than @usr/create-foo.

Expected Behavior

If package name is @usr/create-foo and the value of bin is a string, then the executable name should be @usr/create-foo, according to the package.json documentation. While this is what I expect based on the documentation, I think it is problematic: attempting to execute @usr/create-foo will look for create-foo in a local subdirectory @usr rather finding it in /bin which is in the path - where the globally installed package executables are installed.

npm init @usr/foo and npm exec @usr/create-foo should find the globally installed package and use it if there is no locally installed package of that name. Having found it, they should resolve the executable name consistently with where npm install -g installs it, despite that being inconsistent with the documentation. Given that the package is globally installed, neither command should attempt to download it from the registry.

Installing the executable to the bin directory with the scope refix removed is problematic. Consider the case of several scoped packages named @scope/create for different scopes, for use with npm init @scope. These would be translated to npm exec @scope/create which appears distinct for each scope but if the scope prefix is removed then each executable is simply create and the executables from the various scoped packages will collide. Yet one of the motivations for using scoped packages is exactly to avoid name collisions. Stripping the scope prefix eliminates this advantage. On the other hand, keeping it with the separator character being the same as the system path separator is problematic. Then the executable would be installed into a subdirectory of the bin directory or it would be installed with a name that includes the path separator, which would have to be escaped. Neither is very appealing. The npm exec command at least could find the executable in the .bin directory of the installed package, rather than the global bin directory. That would avoid name conflicts and allow npm init @scope to work as expected. I assume this is effectively what happens when the package is downloaded from the registry: it is downloaded to an npx cache and the executable is run from the copy in that cache, never installed to the global bin directory where it might collide with other such executables.

Steps To Reproduce

1. Create a scoped package named @usr/create-foo with an executable, either with bin value being a string - the path of the script that implements the executable, or an object where key is the same as the package name and value is the same path.
2. Install the package globally with npm install -g . in the root directory of the package
3. Do not publish the package to the registry
4. Confirm that the package has been installed globally, including the executable, though with the 'incorrect' name create-foo rather than @usr/create-foo
5. In an empty directory, run npm init @usr/foo and npm exec @usr/create-foo - both will fail after failing attempted download of the package from the registry, despite it being installed globally.

Environment

• npm: 8.3.1
• Node.js: v16.14.0
• OS Name: Debian GNU/Linux 11 (bullseye)
• System Model Name: Dynabook tecra A50-J
• npm config:

; "user" config from /home/ian/.npmrc

//npm.entrain.nz/:_authToken = (protected) 
//registry.npmjs.org/:_authToken = (protected) 
prefix = "/home/ian/n" 
registry = "https://registry.npmjs.org/" 

; node bin location = /home/ian/n/bin/node
; cwd = /home/ian
; HOME = /home/ian
; Run `npm config ls -l` to show all defaults.

Originally posted by @ig3 in npm/cli#5596

This is the result of my image running.

what`s happen?

Dont see spark typenames post installation

Installed ATLAS using this docker image per instructions for 2.0.0. I see lot of assets in UI including hdfs_path, storm_, etc, etc.

But i dont see spark_db, spark_table etc. What do a ineed to get spark_db, spark_table etc to show up. Any config? IMO spark model is available in ATLAS 2.0.0 onward. https://issues.apache.org/jira/browse/ATLAS-3214

docker run --detach
-p 21000:21000
--name atlas
sburn/apache-atlas
/opt/apache-atlas-2.0.0/bin/atlas_start.py

Apprecaite any help.

Not to able access Atlas GUI with localhost:/21000 - Error The connection was reset.

Hi,

I am running the docker you created on Ubuntu 18.04. Docker run command is successful.
when I connect localhost:/2100.

I get an error message The connection was reset.

Are there any other steps I need to follow to access Apache Atlas UI?

There is an environment variables list. Do I need to configure them?

Any inputs would be helpful.

Running in docker: Hbase issue

Hi,

I run this image in docker(k8s), I met this Hbase issue three times:

• Hbase issue cause port 2181 failed, all connection to this port are refused, this happened twice

• Something wrong with "hbase.regionserver.port", then port 61520 failed, all connection to this port are refused, this happened once

Then I delete pod and it all working properly.

Have you ever met this kind of issue?

Regards,
Liwen Zhao

M1 Mac Docker container not running

On M1 Mac the docker container is running but when you go to localhost:21000 it always results in:
""
This page isn’t working right nowlocalhost didn’t send any data.
ERR_EMPTY_RESPONSE
""

Logs:
2023-01-06 14:11:49 Configured for local HBase.
2023-01-06 14:11:49 Starting local HBase...
2023-01-06 14:11:49 Local HBase started!
2023-01-06 14:11:49
2023-01-06 14:11:49 Configured for local Solr.
2023-01-06 14:11:49 Starting local Solr...
2023-01-06 14:11:49 Local Solr started!
2023-01-06 14:11:49
2023-01-06 14:11:49 Creating Solr collections for Atlas using config: /apache-atlas/conf/solr
2023-01-06 14:11:49
2023-01-06 14:11:49 Starting Atlas server on host: localhost
2023-01-06 14:11:49 Starting Atlas server on port: 21000
2023-01-06 14:21:53 ..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
2023-01-06 14:21:53 Atlas Web-UI startup timed out! But, wait for it...
2023-01-06 14:21:53 Apache Atlas Server process started!
2023-01-06 14:21:53
2023-01-06 14:21:53 Running Apache Atlas with PID 1276...
2023-01-06 14:21:53
2023-01-06 14:21:53 build.user: root
2023-01-06 14:21:53 build.epoch: 1671130609067
2023-01-06 14:21:53 project.version: 2.3.0
2023-01-06 14:21:53 build.version: 2.3.0
2023-01-06 14:21:53 vc.revision: release
2023-01-06 14:21:53 vc.source.url: scm:git:git://git.apache.org/atlas.git/atlas-intg
2023-01-06 14:21:53 ######################################################################################## (Atlas:215)
2023-01-06 14:21:53 2023-01-06 19:11:53,551 INFO - [main:] ~ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (Atlas:216)
2023-01-06 14:21:53 2023-01-06 19:11:53,559 INFO - [main:] ~ Server starting with TLS ? false on port 21000 (Atlas:217)
2023-01-06 14:21:53 2023-01-06 19:11:53,559 INFO - [main:] ~ <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< (Atlas:218)

How can I add new users and set up authentication

I have tried to edit users-credentials.properties file and also updated policy-store.txt inside conf with no luck.

How to enable swagger-UI for atlas Restful API using this docker image?

Hi @sburn ,

I would like to enable swagger-UI for Atlas RESTful API's. Can you please help me with newer version of docker image having this feature? or guide me how I can do it myself?

Thanks,
rajaraddi

Guidance for API authentication in the Readme file would be helpful

Many thanks for this great image!
I'm struggling to set up correctly set authentication credentials to connect to the REST API. I see in pre-conf/atlas-application.properties that atlas.authentication.method.kerberos is set to false and that atlas.authentication.method.file is set to true. I cannot find the "simple" method mentioned in the latest version of the Atlas documentation I found.
So I guess that the default authentication procedure for your docker image consists in registering a username=group::sha256password string in some credential file. But how should we do that ?
I see in your readme that you mention an environment variable "ATLAS_PID_DIR" for PID files, but I don't know what to make of it.
Could you please provide in the readme some indications on how to add/edit users in this setting? That would be very useful to me, and I guess to others.
Best regards

How to integrate hive/hbase/kafka through docker-compose

Hi, after starting this container in docker-compose file, I found that there is no hook package inside the container. So I want to ask about how I can use the hook function to sync the meta-data of hive container.

Persist Weapp modifications

How to persist the webapp modifications?

Not An Issue - Question - APIs

Does this image come with the REST API's as per the Atlas Documentation

Change docker image tag

The update to atlas 2.1.0 was pushed to the docker image 2.0.0. I think it would be beneficial to allow us to still access 2.0.0 for those of us that have built stuff off of that image.

How to change default login

Default login is admin / admin, I cannot find how to change the default, maybe it would be a good thing to include a process for that in the documentation.

Thanks you for your work.

Error at building from your Dockerfile before changing anything to it

Hello @sburn, thanks again for your great work at building this image.
I am trying to build upon this repo to provide a francophone interface to the Apache Atlas UI.
I prepared a script that translates the English labels in the html and javascript files located in opt/apache-atlas-2.1.0/webapp/atlas/js/templates and opt/apache-atlas-2.1.0/webapp/atlas/js/views. I made a fork from your repo, and before appending the translation instruction to your Dockerfile, I first tried to build the image from your original dockerfile on Docker hub. Unfortunately, the building process fails, and the logs end with the following error:

The last line is cropped, it ends with:

Do you have an idea of what might cause this error?
Best regards

docker build failed on aarch64

I've tried to build the image on a Xavier running on aarch64 4.9.140. It fails at least on the missing npm which mvn is not able to install with open-jdk-8. After switching to open-jdk-11 and adding npm to the install list, mvn is able to build atlas.

Windows can use GCC via Cygwin or MSYS2

Windows can use GCC via Cygwin or MSYS2

Originally posted by @ghost in Jamol/kuma#13

Errors in script

https://github.com/sburn/docker-apache-atlas/blob/master/atlas_start.py.patch#L19 and https://github.com/sburn/docker-apache-atlas/blob/master/atlas_start.py.patch#L29
seem to be wrongly indented.

Return 503 after re-create pod

Hi,

Deploy sburn/apache-atlas into kubernetes with PV storage for data and entity:
volumeMounts:
- mountPath: /opt/apache-atlas-2.1.0/data
name: atlas-data
- mountPath: /opt/apache-atlas-2.1.0/solr/server/solr/edge_index_shard1_replica_n1
name: atlas-solr-entity-1
- mountPath: /opt/apache-atlas-2.1.0/solr/server/solr/fulltext_index_shard1_replica_n1
name: atlas-solr-entity-2
- mountPath: /opt/apache-atlas-2.1.0/solr/server/solr/vertex_index_shard1_replica_n1
name: atlas-solr-entity-3
- mountPath: /opt/apache-atlas-2.1.0/solr/server/solr/configsets/_default/conf/managed-schema
subPath: managed-schema
name: managed-schema

The deployment process takes around 15 minutes, then it working fine.

But once I delete the pod and deployment recreate pod, atlas stops working, when I access x.x.x.x:21000, I get 503

Unable to see the Atlas Kafka events

I want to run the image and listen for the Atlas events. If I add an entity I want to see the corresponding event coming out.

Getting HBASE_CONF_DIR not set error while trying to start docker

Error Log:

Exception: ('Could not find hbase-site.xml in %s. Please set env var HBASE_CONF_DIR to the hbase client conf dir', '/opt/apache-atlas-2.0.0/hbase/conf')
Traceback (most recent call last):
File "/opt/apache-atlas-2.0.0/bin/atlas_start.py", line 191, in
returncode = main()
File "/opt/apache-atlas-2.0.0/bin/atlas_start.py", line 95, in main
raise Exception("Could not find hbase-site.xml in %s. Please set env var HBASE_CONF_DIR to the hbase client conf dir", hbase_conf_dir)
Exception: ('Could not find hbase-site.xml in %s. Please set env var HBASE_CONF_DIR to the hbase client conf dir', '/opt/apache-atlas-2.0.0/hbase/conf')