Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synology cpuset no such file #498

Closed
berkutta opened this issue Jan 15, 2019 · 2 comments
Closed

synology cpuset no such file #498

berkutta opened this issue Jan 15, 2019 · 2 comments
Assignees
Labels
kind/bug Issue reporting a bug

Comments

@berkutta
Copy link

berkutta commented Jan 15, 2019

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.

buchdag added a commit to buchdag/acme-companion that referenced this issue Jan 16, 2019
@buchdag buchdag added the kind/bug Issue reporting a bug label Jan 16, 2019
@buchdag buchdag self-assigned this Jan 16, 2019
@buchdag
Copy link
Member

buchdag commented 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.

@berkutta
Copy link
Author

seems to work fine, so can be merged and issue closed imho, thanks!

buchdag added a commit to buchdag/acme-companion that referenced this issue Jan 16, 2019
bingozb pushed a commit to bingozb/docker-letsencrypt-nginx-proxy-companion that referenced this issue Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issue reporting a bug
Projects
None yet
Development

No branches or pull requests

2 participants