Stuck on an issue?
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.
test with docker compose script not working
See original GitHub issueRunning the script ./test_with_docker_compose.sh seems not to be working properly as it exits with code 1:
error: Could not find library geos_c or load any of its variants ['libgeos_c.so.1', 'libgeos_c.so'] neomodel_tests_1 exited with code 1
The full output can be found here.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Run your tests - Docker Documentation
There are unit tests, integration tests and end-to-end testing. In this guide we take a look at running your unit tests in Docker....
Read more >The Ultimate Guide to Integration Testing With Docker ...
I want a one-script solution — no manual steps. It needs to run both locally and on the continuous integration server (Azure DevOps...
Read more >Running tests in containers with docker-compose - JTWay
Enter Docker. Utilizing Docker to run tests can help you to solve these problems. All developers will have the same isolated test environment ......
Read more >Use docker-compose to start test dependencies in gitlab
I would like to run system tests in my pipeline which depends on some running infrastructure (i.e. nifi, mongo-db, etc.).
Read more >Testing with Node and Docker Compose, Part 1
It boils down to running npm test in a Docker container, which may not ... write shell scripts to automate some repetitive docker-compose ......
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 Free
Top 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
Thank you for flagging this, the error is triggered by the tests (and
neomodelfunctionality) of the spatial datatypes. Geos is this one and it gets installed withshapely(or one of its dependencies). Not sure why this is not hapenning when this bash script runs the installation process.Is it possible to manually add
libgeosto the docker image as part of that script?Sounds great @aanastasiou Thanks!