Bug: Export Board menu item - hardcoded host URL breaks with docker
See original GitHub issueThe Export Board
menu item contains a hardcoded URL of the form <root url>/api/boards/<board id>?authToken=<auth-token>
rather than using a relative URL.
This breaks when using Wekan on docker locally since the <root url>
inside the docker container points to http://127.0.0.1
whereas from outside the container, I need to access via something like http://192.168.99.100:8081
.
If i copy the full URL and replace the http://127.0.0.1
with http://192.168.99.100:8081
it works as expected. I guess the simplest fix would be to use relative URLs
Issue Analytics
- State:
- Created 8 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Cannot connect to the Docker daemon using DinD for GitLab ...
I currently self-host all containers in a Rancher (v1.6.28) environment. .gitlab-ci.yml. image: docker:latest ...
Read more >How to Fix and Debug Docker Containers Like a Superhero
Container errors are tricky to diagnose, but some investigative magic works wonders. Read along to learn how to debug Docker containers.
Read more >Overview | Docker Documentation
Select the Docker menu whale menu and then Troubleshoot; Select the Troubleshoot icon from the Docker Dashboard. Troubleshoot Docker Desktop. The Troubleshoot ...
Read more >Docker Context - Docker Documentation
docker context ls NAME DESCRIPTION DOCKER ENDPOINT KUBERNETES ENDPOINT ... There is also an option to export just the Kubernetes part of a...
Read more >docker export - Docker Documentation
Refer to the options section for an overview of available OPTIONS for this command. Description . The docker export command does not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Did you set the
ROOT_URL
environment variable when launching the Wekan Docker container?This issue is very old. AFAIK wekan export of board etc works currently when ROOT_URL is setup correctly.
For Wekan snap related issues, please add new issues to here instead: https://github.com/wekan/wekan-snap/issues
Closing issue.