On 2020-03-25 06:08, Daniel Walsh wrote:
>On 3/24/20 18:28, Philip Rhoades wrote:
>> People,
>>
>> I am making progress with the Podman MTA mentioned in the previous
>> emails (thanks for the help!) - however, I have noticed these errors a
>> few times as I fix / change things and rebuild the image and container:
>>
>> # podman stop indimail
>> 2020-03-24T22:23:00.000955080Z: error opening file
>> '/run/user/0/crun/e75c80ad2b9dc7a79110614459158d1e48cda2c7cabccad64570ea1f91532a24/status':
>> No such file or directory
>> Error: timed out waiting for file
>> /var/run/libpod/exits/e75c80ad2b9dc7a79110614459158d1e48cda2c7cabccad64570ea1f91532a24:
>> internal libpod error
>>
>> - I am not sure but I think on some of the occasions the stop command
>> has not worked and I have had use a more drastic approach . .
>>
>> What should I be looking for to address this issue?
>>
>> Thanks,
>>
>> Phil.
>
>Matt, Any ideas?
>

We're successfully stopping the container, but the exit file is not
being created by Conmon. This could be a Conmon bug where it's
crashing before it can make the file, but that seems unlikely.

Can you add `--log-level=debug` to the `podman stop` command and
provide the results? Is there anything special/interesting about the
container/the way it was started?

Thanks,
Matt Heon
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io