Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker daemon error messages #234

Open
Doodler8888 opened this issue Jul 30, 2024 · 2 comments
Open

Docker daemon error messages #234

Doodler8888 opened this issue Jul 30, 2024 · 2 comments

Comments

@Doodler8888
Copy link

This issue is probably related if not the same as #140.

I don't see any messages originating from the docker daemon. For instance, if I try to delete an image that is used by some container, I will just see this in the messages buffer:

Running: docker image rm 7fb468b501e1 error in process sentinel: docker-process-sentinel: Error running: "docker image rm 7fb468b501e1" (exited abnormally with code 1) error in process sentinel: Error running: "docker image rm 7fb468b501e1" (exited abnormally with code 1)

But it would be pretty handy if it's possible to see the actual error message like:

Error response from daemon: conflict: unable to delete 7fb468b501e1 (must be forced) - image is being used by stopped container 651e2402a695

@Silex
Copy link
Owner

Silex commented Aug 2, 2024

Thanks. Actually the error is logged but in another buffer like * docker image rm 7fb468b501e1 * which is not very convenient.

What should be done is modify https://github.com/Silex/docker.el/blob/master/docker-process.el#L105 and https://github.com/Silex/docker.el/blob/master/docker-process.el#L109 so it prints these messages to some * docker output * buffer instead.

Will try when I have some time.

@Silex
Copy link
Owner

Silex commented Aug 4, 2024

It's actually a bit more complicated than that, but working on something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants