dkcmd: unable to get socket path from environment: Success

Issue #14 resolved
Former user created an issue

I am not sure how to explain this precisely, so please forgive me. In summary, I ran dk for ~24 hours and performed a system update with a kernel update so I rebooted. After reboot, when i start dk, dkrc doesn't seem to be working. It is executable. When I issue dkcmd commands I get the error in the title. I am not sure if this is an issue on my end or not, and if this isn't the appropriate place, again please forgive me.

Comments (1)

  1. Log in to comment