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.
Container stops on github environment: Error response from deamon: Container is not running
See original GitHub issueHi, we’re facing some issues with pipelines ran in github, we’re using GenericContainer to execute some commands on a running container but after the container id is echoed and the command is attempted we get this:
Error response from daemon: Container <> is not running
]
Expecting:
<1>
to be equal to:
<0>
but was not.
Please take a look at our pipeline: https://github.com/spinnaker/clouddriver/pull/5414/checks?check_run_id=2967751843
The pipeline was ran with 1.15.1 but increasing to 1.15.3 didn’t solve the problem. This only happens on github, running locally has no problems.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 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
I increased the log level as requested, but I also increased the k3s ver of the docker image and the error is no longer, we had another error but it’s a test case related issue 😃 https://github.com/spinnaker/clouddriver/pull/5419/checks?check_run_id=3011407918
@danielGz Can you please increase the log level for Testcontainers to debug?
@bsideup Wouldn’t we see an exception if the container is OOM killed?