DevNet Associate DEVASC 200-901 Official Certification Guide by Adrian Iliesiu (z-lib.org)

having to do with the creation of your container, such as
network and runtime environment, mappings, and so on
(as shown in Example 13-5). Be warned: Reading the
output is like reading a container’s DNA.

Example 13-5 docker container inspect Command

Click here to view code image

$ docker container inspect a583eac3cadb

[

{

"Id":

"a583eac3cadbafca855bec9b57901e1325659f76b37705922db67ebf22fdd925",

"Created": "2019-11-

27T23:35:12.537810374Z",

"Path": "bash",

"Args": [],

"State": {

"Status": "exited",

"Running": false,

"Paused": false,

"Restarting": false,

"OOMKilled": false,

"Dead": false,

"Pid": 0,

"ExitCode": 127,

"Error": "",

"StartedAt": "2019-11-

27T23:35:13.185535918Z",

"FinishedAt": "2019-11-

27T23:53:15.898516767Z"

},

"Image":

"sha256:775349758637aff77bf85e2ff0597e86e3e859183ef0baba8b3e8fc8d3c

ba51c",

"ResolvConfPath":

"/var/lib/docker/containers/a583eac3cadbafca

855bec9b57901e1325659f76b37705922db67ebf22fdd925/resolv.conf"

<cut for brevity>

The logs command details everything the container
recorded as output and is super helpful for catching error
messages: