Problem running docker-compose for local tests (using current master branch)
See original GitHub issueUbuntu 18.04 LTS.
Clean run of docker-compose
after docker system prune -a
.
See attachment (too long to paste):
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
docker-compose is not able to resolve Git URIs from TFS ...
I have a repository on TFS with a dockerfile that works when you pull it manually and run it. So, git clone ......
Read more >Announcing Compose V2 General Availability - Docker
Here's what Docker Compose V2's graduation means for you: The Docker Compose V2 branch is now the default on GitHub. You can still...
Read more >Using the Fabric test network - Hyperledger Fabric Docs
Because the nodes are isolated within a Docker Compose network, the test network is not configured to connect to other running Fabric nodes....
Read more >1.3. First Buildbot run with Docker
If you're having trouble, first determine whether it is a Buildbot issue or a Docker issue ... This tutorial uses docker-compose to run...
Read more >Getting Started - IOTstack
It is just that IOTstack gets most of its testing under these conditions. ... The menu is used to install Docker and then...
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
@hroff-1902 From your log, it seems that the container image has been built just fine! Those errors when building the image are irrelevant:
Also, when building the container, it does not execute the tests, it only installs all the required dependencies. So after you get to the container’s shell, you can execute the
npm run build
to build the sources, and then (for running the tests for various languages):I also just changed the
run-tests
behavior a bit in f6de83d629e2bc0e478a9d93309983c0944e2749, so that it does not burn the CPU too hard — so please update.@xpl Thanks, I’ll repeat the actions on my next PR and verify.