search

frappe / frappe_docker

Docker images for production and development setups of the Frappe framework and ERPNext
MIT License
1.49k stars 1.38k forks source link

unable to access http://development.localhost:8000 in dev development #1469

Open sourabhmandal opened 2 months ago

sourabhmandal commented 2 months ago

Description of the issue

Trying to access http://development.localhost:8000 from browser loads infinitely when running dev-container

Context information (for bug reports)

I followed the steps mentioned in Development container. However after running the bench start command I am not able to access the website in host machine. However if I do a curl http://development.localhost:8000 inside container itself I am getting a response with HTML page.

PS: I am using MacOS as host machine

Steps to reproduce the issue

  1. Take a macOS laptop
  2. cp -R devcontainer-example .devcontainer
  3. cp -R development/vscode-example development/.vscode
  4. open .devcontainer/docker-compose.yml and comment out MariaDB and its volume and uncomment PostgresDB and its volume
  5. Run dev container in VS code with appropriate extensions as mentioned
  6. Inside container run bench init --skip-redis-config-generation frappe-bench && cd frappe-bench
  7. setup host 
    bench set-config -g db_host mariadb
bench set-config -g redis_cache redis://redis-cache:6379
bench set-config -g redis_queue redis://redis-queue:6379
bench set-config -g redis_socketio redis://redis-queue:6379
  8. Create new site bench new-site --db-type postgres --db-host postgresql development.localhost
  9. set root password 
    bench config set-common-config -c root_login postgres
bench config set-common-config -c root_password '"123"'
  10. set dev mode in site 
    bench --site development.localhost set-config developer_mode 1
bench --site development.localhost clear-cache
  11. bench start
  12. go to http://development.localhost:8000 in host machine

Observed result

Expected result

maheini commented 1 month ago

Thanks for providing such good information. Based on the fact that you are able to request at least some html within the container - I'd expect the problem to be docker or system based. You should at least get a 500 http response if the container is accessible from outside.

Can you check the exposed ports, matching ip address (is development.localhost even mapped to this container?)?

Please be aware, I'm using docker for windows, but there shouldn't be any big differences.

revant commented 1 month ago

I'll not be able to help anyone using Mac or windows.