HTTP ERROR: 503 Problem accessing /login.jsp about atlas-docker HOT 5 OPEN

Correct,
The compose file is to run atlas as a component of a build. I am aware that it is not dependant on other services but was looking to integrate it to other services (i.e., auto discovery / hooks into Kafka).

Running the image individually through docker run worked and funnily enough it works if it is the only service in docker-compose. I will look into this a little deeper next week or so.

from atlas-docker.

hi @Spydernaz,
not sure exactly what are you trying achieve with the docker-compose with all the services configured there that you listed. This image I build is meant to be used for a container executed on its own and does not depend on any services that you would need to run with compose.
The atlas binaries are built with embedded-cassandra-solr option as documented here https://atlas.apache.org/InstallationSteps.html and is and configured to use local&embedded solr and cassandra.
Could you maybe share the full compose file and a bit more details on the commands that you run and their sequence.
The image is mainly meant to be used for learning about atlas and for testing an development maybe.
Did you get the same errors in the log files when creating & running the container using the following docker run command?
docker run --name atlas200 -p 21000:21000 -d mmiklas/atlas-docker:v2.0.0

from atlas-docker.

Hi michalmiklas,

I did not change the docker file. I just executed the command you mentioned.
for v2.0 released on 2019-05-14 (with Solr 7.5):
docker run --name atlas200 -p 21000:21000 -d mmiklas/atlas-docker:v2.0.0

Not able to connect to the localhost:21000.

Can you please provide some inputs on how to resolve this error and Open Atlas GUI

from atlas-docker.

hi @SalmaSattar
I honestly have no idea why you should be getting this error and having problems with the image/container execution. I tried again just now and all is working perfectly for me.

The host environment I am running this in container on is a RHEL7.5 and using docker-ce. But I cannot imagine how this could have impact on whats happening inside the container.
(am I correct to assume your docker is running on windows? using vbox for linux env virtualization?)

Would suggest two things:

1. try to run it in a RHEL 7.5. host machine
2. try to remove your container and image and try to download and run it again

No other suggestions for now.

from atlas-docker.

So, this is still n intermittent error I received, often when running a docker compose... My assumption is that it has something to do with Cassandra wanting to reserve memory?

Not sure if this will help, but I have a different image being built using hbase instead and have noted more stability in my compose files, might help you to

https://github.com/Spydernaz/docker_images/tree/master/apache-atlas

Note: @michalmiklas advice works for me, just inconsistently and almost never in a compose file. The above image however takes forever to build and start (guessing it is the hbase?)

from atlas-docker.