How to get the exit code of a non-running Docker container
php editor Xiaoxin introduces you how to get the exit code of a Docker container that is not running. When using Docker, sometimes we need to view the exit code of the container when it exits for troubleshooting or debugging. However, when the container is not running, we cannot directly use the `docker logs` command to get the exit code. In this article, we will introduce a method to get the exit code of a non-running Docker container to help you better deal with container-related issues.
Question content
I need to get the exit code of a container that is in a non-running state. I know the container is not running, I am getting this information from different sources.
Is there a way in Docker's go SDK to get the exit code without having to wait for the container to be in a certain state?
For example, what does WaitResponse
of ContainerWait
provide?
Is it a good solution to simply call ContainerWait
when my container no longer exists? Or is there a better solution?
I'm particularly interested in avoiding ContainerWait
because I can see that call being very expensive.
Each container call to consting takes approximately 10 milliseconds if the container's state is stopped, and 20 to 50 milliseconds if the container is restarted.
Solution
The exit code is located in the containerstate
structure. This is embedded in the state field in the <code>
response(*client).containerinspect().
For example:
func checkExitStatus(ctx context.Context, client *client.Client, containerID string) error { inspection, err := client.ContainerInspect(ctx, containerID) if err != nil { return err } // Possible values are listed in the `ContainerState` docs; there do not // seem to be named constants for these values. if inspection.State.Status != "exited" { return errors.New("container is not exited") } if inspection.State.ExitCode != 0 { return fmt.Errorf("container exited with status %d", inspection.State.ExitCode) } return nil }
The above is the detailed content of How to get the exit code of a non-running Docker container. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...
