Paul Seidler

So to give you a proper number: about 80.000€. That should suffice for paying a developer half a year. Anyways, thanks for all your efforts. **I really appreciate it**. Maybe...

> This appears to be addressed with #12657 and would just need to be backported to 17. It's now part of [17.10.0](https://docs.chef.io/release_notes_client/#17.10.0)

@tpowell-progress maybe to make it a little bit more clear the version in use includes the proposed fix. So it's not fixed. I did a little bit testing on my...

Ok I did some digging and the source seems to be [located in these cases](https://github.com/chef/chef/blob/0cefcaa319b0d2f07241b78bf7d6f06de03d07ef/lib/chef/provider/package.rb#L486). There is simply no path for the case where the package is already installed but...

So I dug a bit deeper and got some nightmares ;) but even through here my findings & conclusions. First the issue does not appear if you do not specify...

I can confirm that `kitchen destroy` still not properly cleans up the `~/.dokken` cache witch cinc-workstation 22.10.1013 and so source updates are not properly propagated as the files are not...

For me that's still the case. My workaround is specifying all configuration paramaters in the `daemon.json` via: ``` docker_daemon_options: containerd: "/run/containerd/containerd.sock" hosts: [ "tcp://127.0.0.1:2375", "unix:///var/run/docker.sock" ] ``` and the following...

@epou Nice thanks! I guess you would need a restart instead of a reload of Docker. Else I suspect the process would still be running with the default parameters.

Stupid me confussed `systemctl reload` with `systemctl daemon-reload` and got confussed by the fact that there is no restart of `docker` itself. Thanks for correcting me!

The workaround should be to change in `/usr/src/evdi-1.13.1/evdi_drm.h` the line: ``` #include "drm.h" ``` to ``` #include ``` Remove the dkms module again to force a recreation: ``` dkms remove...