Issue not solved, but closed

[henfri]

• This is a bug report
• This is a feature request
• I searched existing issues before opening this one

Expected behavior

The bug at
#679
still exist. It should be re-opened.
I cannot request a re-opening of the bug and I fear that it will not be seen by maintainers.

Actual behavior

It was closed, but not solved
#679

Steps to reproduce the behavior

Install and use docker in debian, check the logs

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.)

[ghost]

i don't think this should be here

[henfri]

What alternative do you propose?

[ghost]

commenting on the issue instead of making a whole new issue?

[henfri]

Well, I suspect that closed issues are not monitored by the maintainers. At least I cannot see any further progress/interest here. So I was not sure how else to raise attention to this topic.

If you have a suggestion, I will take that into account in future.
I am happy to close this one, once the other one is re-opened. If you think that this is inappropriate, please close this one. But I'd be interested in the reason then.

Regards,
Hendrik

[shadowlmd]

I can confirm that the issue is still not resolved and is quite annoying.

[cpuguy83]

This does not look like a docker bug.
Docker is just calling the mount system call, systemd itself is spamming the logs when it detects that something was mounted.
The problem lies with systemd auto-generating these mount units, which docker itself is not doing.

Closing since the discussion belongs in the other issue... but again there is nothing docker can change to make these logs not happen.