This repository has been archived by the owner. It is now read-only.
cannot find sdnotify-proxy in /usr/libexec #1528
Closed
Comments
Experience the same issue on bare-metal installations. Due to this bug flanneld cannot start, thus subsequent processes such as docker and kubernetes will fail too. |
@vcaputo When can I expect this fix to be released? |
@vcaputo Also, does |
I don't think docker's using runc makes any difference WRT sdnotify-proxy, the client-server architecture of docker is unchanged AFAIU. |
@voith The change is slated for the next beta, in two weeks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Report
Bug
cannot find sdnotify-proxy in /usr/libexec. Has coreos stopped shipping sdnotify-proxy?
CoreOS Version
Environment
What hardware/cloud provider/hypervisor is being used to run CoreOS?
cloud provider: Digital Ocean
Expected Behavior
expected to find sdnotify-proxy in /usr/libexec
Actual Behavior
-bash: /usr/libexec/sdnotify-proxy: No such file or directory
Reproduction Steps
The text was updated successfully, but these errors were encountered: