-
Notifications
You must be signed in to change notification settings - Fork 15
cc-proxy: Fix systemd socket and service #43
Conversation
Some paths provided in the cc-proxy.service and cc-proxy.socket were both relying on legacy path names from cc-oci-runtime. This directly led the cc-proxy service to be not started as expected when the proxy socket was used. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
cc-proxy.service.in
Outdated
|
|
||
| [Service] | ||
| ExecStart=@libexecdir@/cc-proxy | ||
| ExecStart=@libexecdir@/clearcontainers/cc-proxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we standardise on clear-containers? see clearcontainers/runtime#85
Makefile
Outdated
|
|
||
| SOURCES := $(shell find . 2>&1 | grep -E '.*\.(c|h|go)$$') | ||
| PROXY_SOCKET := $(LOCALSTATEDIR)/run/clearcontainers/proxy.sock | ||
| PROXY_SOCKET := $(LOCALSTATEDIR)/run/$(CLEARCONTAINERS_SUFFIX)/proxy.sock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/_SUFFIX// that's not really a suffix DIR maybe? or just have clear-containers everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're fine with hardcoding this "clear-containers" everywhere, I am fine with it.
@jodh-intel any thought on this ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rename to something like CLEAR_CONTAINERS_DIR for legibility.
|
I'm absolutely fine with this |
Because it has been decided that clear-containers will be cleaner and because we want to be consistent accross all projects, let's replace "clearcontainers" with "clear-containers". Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
|
@dlespiau Does that sound good now ? |
Some paths provided in the cc-proxy.service and cc-proxy.socket were both relying on legacy path names from cc-oci-runtime. This directly led the cc-proxy service to be not started as expected when the proxy socket was used.