Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"No module named yaml" - not loading correct docker_base_image?
See original GitHub issueAgain, running locally on redux branch:
When I try to launch an experiment, get a ImportError: No module named yaml when App.py is called.
pyyaml is in the requirements.txt in base_docker_image, so not sure why this would be.
Learning from the last issue, I compared the ec2 docker-compose to the local docker-compose: The former has:
minionworker:
build: next/base_docker_image
The latter has:
minionworker:
build: /home/ubuntu/NEXT/next/base_docker_image
(same for nextbackenddocker, which is also showing the import error)
So I thought this was the issue… calling the wrong requirements file or something… tried playing around with a few things with no luck.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@lalitkumarj figured it out. The redux version was trying to launch on the docker images built with the master version… I deleted the docker images and rebuilt them using the redux Dockerfile and it works now.
Also tried adding:
python-yamlto the Dockerfile, which should install the ubuntu package containing that module… no luck