You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to use the container on a Synology NAS I'm getting the following error:
cat: /proc/1/cpuset: No such file or directory
2019/01/15 20:59:40, Error: can't get my container ID !
Is there any workaround for that? I assume this is a Synology specific thing. If I enter via bash to the container I can verify that there is no cpuset in the path.
The text was updated successfully, but these errors were encountered:
buchdag
added a commit
to buchdag/acme-companion
that referenced
this issue
Jan 16, 2019
I've pushed an image with a possible fix to duch/letsencrypt-nginx-proxy-companion:496, could you pull this image and try again ? I'll PR and merge the fix if it works ok.
When trying to use the container on a Synology NAS I'm getting the following error:
Is there any workaround for that? I assume this is a Synology specific thing. If I enter via bash to the container I can verify that there is no cpuset in the path.
The text was updated successfully, but these errors were encountered: