mozilla / addons

☂ Umbrella repository for Mozilla Addons ✨
Other
127 stars 41 forks source link

ERROR: No container found for web_1 #6517

Closed miphilomath closed 4 years ago

miphilomath commented 5 years ago

Describe the problem and steps to reproduce it:

While setting up the project following the steps as per https://addons-server.readthedocs.io/en/latest/topics/install/docker.html, above said error is popping up.

What happened?

[philomath@cosmos addons-server]$ make initialize_docker 
docker-compose exec web make initialize
ERROR: No container found for web_1
make: *** [Makefile-os:57: initialize_docker] Error 1
[philomath@cosmos addons-server]$ vim Makefile-os
[philomath@cosmos addons-server]$ docker-compose logs | grep web_1
Attaching to addons-server_addons-frontend_1_8949804df0f8, addons-server_web_1_a6af281cab15, addons-server_rabbitmq_1_799671fa1b1a, addons-server_elasticsearch_1_5d329b7b1647, addons-server_autograph_1_1be3fa52d282, addons-server_worker_1_673a53aec5a0, addons-server_memcached_1_11a72674bcc3, addons-server_nginx_1_d33b30ec7dee, addons-server_mysqld_1_3331bcf31c90, addons-server_redis_1_75c2b67a4b2f
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied
web_1              | /bin/bash: ./scripts/start-docker.sh: Permission denied

On running the script,

[philomath@cosmos addons-server]$ sudo ./scripts/start-docker.sh
useradd: UID 1000 is not unique
id: ‘olympia’: no such user
Starting with user: 'olympia' uid: 
su: user olympia does not exist

What did you expect to happen?

Run the command with success.

Anything else we should know?

I guess, the error is related to user permission somehow, but I am not sure. If it is, we might need to update the docs as well.

junngo commented 5 years ago

I think that you don't run docker container. (Check docker state docker ps) You should execute command docker-compose up -d to run docker container.

diox commented 5 years ago

@miphilomath as @junngo said, did you execute docker-compose up -d first? In any case you should not try to run ./scripts/start-docker.sh manually, it's an entry point for the docker container, not something you should run yourself.

miphilomath commented 5 years ago

Yes, I did. I followed all the steps as instructed here.

dsychin commented 5 years ago

I am encountering the same problem trying to run the server locally on windows. I thought that it was a windows problem. I can access the website at olympia.test but pretty much anything I do generates an error. I haven't had the time to try it on linux yet.

UPDATE: I was able to get it working in Ubuntu. Have you tried running with sudo? sudo make initialize_docker

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. If you think this bug should stay open, please comment on the issue with further details. Thank you for your contributions.

bhushan-borole commented 4 years ago

Hello, I am running the command docker-compose up -d, but still I am getting this error. Can somebody help me fix this error? Thank you

Mohammadnim123 commented 4 years ago

Just docker-compose restart

Ssousuke commented 2 years ago

Just docker-compose restart

Thanks

nicocasel commented 1 year ago

If it can help, I had the same issue because my containers were not up (I thought they were, but they were not actually). So, as other people already said, running this command solved it: docker-compose up -d