Can't run on Docker

[mateomorrison]

Successfully ran Nicistore on a Docker container. Simple as clone, cd folder, build and run.

Tried same steps on Atlas. But clearly it's not installing itself. It runs, but nothing shows on port 8000. My steps:

1. git clone this rep
2. cd the rep folder
3. git build the rep
4. git run -d --name atlas -p 8000:8000 -t yoonic/atlas

Something I'm doing wrong? Maybe I have to run RethinkDB and Atlas in the same container?

[mateomorrison]

@andreftavares Never received support on this! Need help

[mateomorrison]

This is not working on Docker. Even after pull, build and start (and yea also restart)

RethinkDB is listening on port 8080, Nicistore on port 3000 and Atlas was set to listen at port 8000, seem that is not running. @andreftavares Help!

[andrecrt]

The Dockerfile provided by both Atlas and Nicistore are the ones being used in the Live/Demo site. Docker is a topic outside of the realm of these apps, an operational issue and not mandatory for running them.

[mateomorrison]

I know that it's outside of the palm. But it's supposed to get running. I'm trying to hack this around and nobody can understand the code more than the creator.

When trying to get the logs, throw this:

2017-03-04 23:57:05,027 INFO spawned: 'atlas' with pid 9197 2017-03-04 23:57:06,029 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:07,689 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:08,693 INFO spawned: 'atlas' with pid 9207 2017-03-04 23:57:09,695 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:11,533 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:12,536 INFO spawned: 'atlas' with pid 9217 2017-03-04 23:57:13,539 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:15,527 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:16,532 INFO spawned: 'atlas' with pid 9227 2017-03-04 23:57:17,534 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:20,327 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:21,331 INFO spawned: 'atlas' with pid 9237 2017-03-04 23:57:22,333 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:23,932 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:24,935 INFO spawned: 'atlas' with pid 9247 2017-03-04 23:57:25,937 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:27,567 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:28,571 INFO spawned: 'atlas' with pid 9257 2017-03-04 23:57:29,574 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:31,202 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:32,206 INFO spawned: 'atlas' with pid 9267 2017-03-04 23:57:33,208 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:34,902 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:35,905 INFO spawned: 'atlas' with pid 9277 2017-03-04 23:57:36,907 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:37,700 WARN received SIGTERM indicating exit request 2017-03-04 23:57:37,701 INFO waiting for atlas to die 2017-03-04 23:57:37,705 INFO stopped: atlas (terminated by SIGTERM) 2017-03-04 23:57:38,089 CRIT Supervisor running as root (no user in config file) 2017-03-04 23:57:38,089 WARN Included extra file "/etc/supervisor/conf.d/atlas.conf" during parsing 2017-03-04 23:57:38,099 INFO RPC interface 'supervisor' initialized 2017-03-04 23:57:38,100 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2017-03-04 23:57:38,100 INFO supervisord started with pid 1 2017-03-04 23:57:39,103 INFO spawned: 'atlas' with pid 7 2017-03-04 23:57:40,105 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-03-04 23:57:41,705 INFO exited: atlas (exit status 1; not expected) 2017-03-04 23:57:42,708 INFO spawned: 'atlas' with pid 17 2017-03-04 23:57:43,710 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

It gets running but it doesn't show on port :8000

I'm just trying to understand this code fully to get to build more fun stuff to your open source app. Doesn't have to be you @andreftavares but anybody that has more comprehension on Docker.

[mateomorrison]

I can run Nicistore and RethinkDB on Docker Machine with Nginx and Lets Encrypt. I just need help with uploading images and deploying Atlas on Docker, please.

El El sáb, 4 de mar. de 2017 a las 06:55, André Tavares < notifications@github.com> escribió:

The Dockerfile provided by both Atlas and Nicistore are the ones being used in the Live/Demo site. Docker is a topic outside of the realm of these apps, an operational issue and not mandatory for running them.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/yoonic/atlas/issues/14#issuecomment-284144090, or mute the thread https://github.com/notifications/unsubscribe-auth/AX0pHwJfXvcNjytUYjt4QDew6-clamPCks5riUMQgaJpZM4MQX7U .

-- Mateo Morrison CEO at Tasky Exec Chairman at Fangoo

[phoenixvk]

How did you resolve above issue @mateomorrison I'm also getting that app is running on 0.0.0.0:8000 but shows nothing

[phoenixvk]

anybody stuck on this? Did anybody find something?

[phoenixvk]

@andreftavares Will you please provide gist for this to run in prod?

[mateomorrison]

Atlas is not runnig at all on Docker. This is the unique problem I'm experiencing. I will reply your questions about nicistore, and can help you deplying RethinkDB with Docker too El El mié, 29 de mar. de 2017 a las 4:41 p.m., phoenixvk < notifications@github.com> escribió:

@andreftavares https://github.com/andreftavares Will you please provide gist for this to run in prod?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/yoonic/atlas/issues/14#issuecomment-290219174, or mute the thread https://github.com/notifications/unsubscribe-auth/AX0pHxQSpf4o3lX1w1tNaAyYwtQzDGlhks5rqsIEgaJpZM4MQX7U .

-- Mateo Morrison CEO at Tasky Exec Chairman at Fangoo

[phoenixvk]

I have deployed nicisrore using docker with letsencrypt. But I'm getting same problem that you have(only for Atlas) .

[phoenixvk]

1. git run -d --name atlas -p 8000:8000 -t yoonic/atlas

Mateo you are doing above in 1st comment and 4th step resolve it.

[phoenixvk]

it should be docker

[phoenixvk]

Any luck?

[jujes]

here the same issue:

2017-05-08 21:27:08,403 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:09,406 INFO spawned: 'atlas' with pid 709
2017-05-08 21:27:10,408 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:10,927 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:11,930 INFO spawned: 'atlas' with pid 719
2017-05-08 21:27:12,932 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:13,427 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:14,430 INFO spawned: 'atlas' with pid 729
2017-05-08 21:27:15,951 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:15,982 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:16,984 INFO spawned: 'atlas' with pid 739
2017-05-08 21:27:18,434 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:18,464 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:19,467 INFO spawned: 'atlas' with pid 749
2017-05-08 21:27:20,468 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:20,963 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:21,966 INFO spawned: 'atlas' with pid 759
2017-05-08 21:27:22,967 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:23,486 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:24,487 INFO spawned: 'atlas' with pid 769
2017-05-08 21:27:25,489 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:26,045 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:27,047 INFO spawned: 'atlas' with pid 779
2017-05-08 21:27:28,049 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:28,550 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:29,553 INFO spawned: 'atlas' with pid 789
2017-05-08 21:27:30,958 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:30,988 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:31,991 INFO spawned: 'atlas' with pid 799
2017-05-08 21:27:33,405 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:33,434 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:34,437 INFO spawned: 'atlas' with pid 809
2017-05-08 21:27:35,877 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:35,910 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:36,912 INFO spawned: 'atlas' with pid 819
2017-05-08 21:27:37,913 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:38,442 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:39,445 INFO spawned: 'atlas' with pid 829
2017-05-08 21:27:40,849 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:40,880 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:41,883 INFO spawned: 'atlas' with pid 839
2017-05-08 21:27:42,885 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:43,459 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:44,461 INFO spawned: 'atlas' with pid 849
2017-05-08 21:27:45,904 INFO success: atlas entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-08 21:27:45,936 INFO exited: atlas (exit status 1; not expected)
2017-05-08 21:27:46,938 INFO spawned: 'atlas' with pid 859
2017-05-08 21:27:48,349 INFO success: atlas entered RUNNING state, proce

[cogitamus]

This PG might help https://github.com/yoonic/atlas/pull/7

[mateomorrison]

Atlas doesn't run on docker. And the GP does not give any solution

El El mar, 9 de may. de 2017 a las 6:59 a.m., cogitamus < notifications@github.com> escribió:

This PG might help #7 https://github.com/yoonic/atlas/pull/7

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/yoonic/atlas/issues/14#issuecomment-300130442, or mute the thread https://github.com/notifications/unsubscribe-auth/AX0pH5f01Rw29QaiQLUQV_9g1h1fcSRkks5r4EctgaJpZM4MQX7U .

-- Mateo Morrison CEO at Tasky Exec Chairman at Fangoo