[GH-ISSUE #387] Docker Container cannot start #197

Closed
opened 2026-02-26 10:30:54 +03:00 by kerem · 13 comments
Owner

Originally created by @BentiGorlich on GitHub (Oct 5, 2021).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/387

Do you want to request a feature or report a bug?
bug
What is the current behavior?
When I try to start the docker container, I get this error message: docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: operation not permitted: unknown.
My start command: sudo docker run -i -t -d -p 8002:443 --restart=always -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql onlyoffice/documentserver:6.3.0

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

What is the expected behavior?
it starts the docker container
Did this work in previous versions of DocumentServer?
yes
DocumentServer Docker tag:
tried 6.3, 6.3.0, latest
Host Operating System:
debian10u2

I updated a bunch of libraries, but why would that get me that error. Any help is appreciated.

Originally created by @BentiGorlich on GitHub (Oct 5, 2021). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/387 **Do you want to request a *feature* or report a *bug*?** bug **What is the current behavior?** When I try to start the docker container, I get this error message: `docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: bpf_prog_query(BPF_CGROUP_DEVICE) failed: operation not permitted: unknown.` My start command: ` sudo docker run -i -t -d -p 8002:443 --restart=always -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql onlyoffice/documentserver:6.3.0` **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.** **What is the expected behavior?** it starts the docker container **Did this work in previous versions of DocumentServer?** yes **DocumentServer Docker tag:** tried 6.3, 6.3.0, latest **Host Operating System:** debian10u2 I updated a bunch of libraries, but why would that get me that error. Any help is appreciated.
kerem closed this issue 2026-02-26 10:30:54 +03:00
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

This is new for me, but I don't think it's our problem, maybe error in Docker itself

I've found something like this:
https://stackoverflow.com/questions/67791683/docker-container-starting-issue-setting-cgroup-config-for-prochooks-process-cau

I think you first should update your host os to latest version of docker and contained

P.S. To be clear - your host OS is not ARM-based?

<!-- gh-comment-id:934424996 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): This is new for me, but I don't think it's our problem, maybe error in Docker itself I've found something like this: https://stackoverflow.com/questions/67791683/docker-container-starting-issue-setting-cgroup-config-for-prochooks-process-cau I think you first should update your host os to latest version of docker and contained P.S. To be clear - your host OS is not ARM-based?
Author
Owner

@BentiGorlich commented on GitHub (Oct 5, 2021):

Hello,
I had trouble to find stuff that is truly connected to my issue. The problem is it sounds like something with cgroup, but I do not have cgroup installed...
I already tried to fully reinstall docker and it didn't change anything.

No I am running on x86 (Intel NUC)

<!-- gh-comment-id:934446808 --> @BentiGorlich commented on GitHub (Oct 5, 2021): Hello, I had trouble to find stuff that is truly connected to my issue. The problem is it sounds like something with cgroup, but I do not have cgroup installed... I already tried to fully reinstall docker and it didn't change anything. No I am running on x86 (Intel NUC)
Author
Owner

@BentiGorlich commented on GitHub (Oct 5, 2021):

Upgrading my OS does sound like a risk and it took a long time for me to setup the server. Additionally it hosts a bunch of data that I can't afford to loose. That lays on a virtual raid array and I didn't have the time yet to backup the config for that. I tried to, but didn't get the infos on google that I needed, so it got in the basket of things I have to do

<!-- gh-comment-id:934449028 --> @BentiGorlich commented on GitHub (Oct 5, 2021): Upgrading my OS does sound like a risk and it took a long time for me to setup the server. Additionally it hosts a bunch of data that I can't afford to loose. That lays on a virtual raid array and I didn't have the time yet to backup the config for that. I tried to, but didn't get the infos on google that I needed, so it got in the basket of things I have to do
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

Could you try this on another server?

Generally speaking this error is raised from docker program itself, so I'm 95% sure it's not related to DocumentServer

<!-- gh-comment-id:934449650 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): Could you try this on another server? Generally speaking this error is raised from docker program itself, so I'm 95% sure it's not related to DocumentServer
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

And I'm not mean upgrading your system, but updating. This shouldn't be a risk.

At least make sure that you've using latest version of docker packages

<!-- gh-comment-id:934455975 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): And I'm not mean upgrading your system, but updating. This shouldn't be a risk. At least make sure that you've using latest version of docker packages
Author
Owner

@BentiGorlich commented on GitHub (Oct 5, 2021):

Ok. Yeah I did that and that's when docker began to give me that error message.
I ran a complete

sudo apt-get update
sudo apt-get upgrade
<!-- gh-comment-id:934458162 --> @BentiGorlich commented on GitHub (Oct 5, 2021): Ok. Yeah I did that and that's when docker began to give me that error message. I ran a complete ``` sudo apt-get update sudo apt-get upgrade ```
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

Ok in that case I'm almost sure this is issue in docker side and you should report it appropriate repo

<!-- gh-comment-id:934462932 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): Ok in that case I'm almost sure this is issue in docker side and you should report it appropriate repo
Author
Owner

@BentiGorlich commented on GitHub (Oct 5, 2021):

ok, then I will try to get an answer from there. I thought you may have an idea whats causing this. Thanks for the answers :)

<!-- gh-comment-id:934467876 --> @BentiGorlich commented on GitHub (Oct 5, 2021): ok, then I will try to get an answer from there. I thought you may have an idea whats causing this. Thanks for the answers :)
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

I thought you may have an idea whats causing this

No sorry, never saw an error like this in our app
And docker itself is a very complicated tool, so reason may be anything

The only advice I have - try to set up new server with Debian 10 and see in clear setup if everything works fine - if not maybe this problem is more global than your machine

<!-- gh-comment-id:934475422 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): > I thought you may have an idea whats causing this No sorry, never saw an error like this in our app And docker itself is a very complicated tool, so reason may be anything The only advice I have - try to set up new server with Debian 10 and see in clear setup if everything works fine - if not maybe this problem is more global than your machine
Author
Owner

@ShockwaveNN commented on GitHub (Oct 5, 2021):

Also I found this

https://github.com/opencontainers/runc/issues/3008

So as far as I understand it depends on combination of system kernel and docker service version, but this may be another error

<!-- gh-comment-id:934480401 --> @ShockwaveNN commented on GitHub (Oct 5, 2021): Also I found this https://github.com/opencontainers/runc/issues/3008 So as far as I understand it depends on combination of system kernel and docker service version, but this may be another error
Author
Owner

@dreua commented on GitHub (Oct 6, 2021):

Did you check with another docker image, e.g. hello-world?

<!-- gh-comment-id:936718125 --> @dreua commented on GitHub (Oct 6, 2021): Did you check with another docker image, e.g. hello-world?
Author
Owner

@BentiGorlich commented on GitHub (Oct 6, 2021):

Yeah, I created an issue on the https://github.com/moby/moby/ repo and they asked the same. The hello-world image did throw the same error. So it is definatley not an only office issue.
https://github.com/moby/moby/issues/42909

<!-- gh-comment-id:936721835 --> @BentiGorlich commented on GitHub (Oct 6, 2021): Yeah, I created an issue on the https://github.com/moby/moby/ repo and they asked the same. The `hello-world` image did throw the same error. So it is definatley not an only office issue. https://github.com/moby/moby/issues/42909
Author
Owner

@ShockwaveNN commented on GitHub (Oct 7, 2021):

@BentiGorlich Got it, thanks

P.S. I think you should change title of issue at moby repo since seems this is not related to ONLYOFFICE DocumentServer

<!-- gh-comment-id:937498320 --> @ShockwaveNN commented on GitHub (Oct 7, 2021): @BentiGorlich Got it, thanks P.S. I think you should change title of issue at moby repo since seems this is not related to ONLYOFFICE DocumentServer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#197
No description provided.