[GH-ISSUE #251] Wrong permissions for docker image: redis refuses to start #141

Closed
opened 2026-02-26 09:36:53 +03:00 by kerem · 6 comments
Owner

Originally created by @marcoconstancio on GitHub (May 28, 2020).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/251

Do you want to request a feature or report a bug?
bug

What is the current behavior?
redis refuses to start, returns Waiting for connection to the localhost host on port 5432 error and as a result the document server does not start.

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

What is the expected behavior?
Redis server starting normally

Did this work in previous versions of DocumentServer?
Not sure

DocumentServer version:
Latest

Operating System:
Debian

Fix:
Setting the 644 permission on the /etc/hosts file

Originally created by @marcoconstancio on GitHub (May 28, 2020). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/251 **Do you want to request a *feature* or report a *bug*?** bug **What is the current behavior?** redis refuses to start, returns **Waiting for connection to the localhost host on port 5432** error and as a result the document server does not start. **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.** Starting or rebuilding the docker image **What is the expected behavior?** Redis server starting normally **Did this work in previous versions of DocumentServer?** Not sure **DocumentServer version:** Latest **Operating System:** Debian **Fix:** Setting the 644 permission on the **_/etc/hosts_** file
kerem closed this issue 2026-02-26 09:36:53 +03:00
Author
Owner

@ShockwaveNN commented on GitHub (May 29, 2020):

This is strange, never seen problem like this.
Could you attach full docker run command you're using

<!-- gh-comment-id:635803665 --> @ShockwaveNN commented on GitHub (May 29, 2020): This is strange, never seen problem like this. Could you attach full `docker run` command you're using
Author
Owner

@marcoconstancio commented on GitHub (May 29, 2020):

I'm not using docker on command line, I'm using portainer on my openmediavault instalation. Not sure it helps, but I placed the portainer inspect section of that image in https://pastebin.com/mwTvrUrF

<!-- gh-comment-id:635934696 --> @marcoconstancio commented on GitHub (May 29, 2020): I'm not using docker on command line, I'm using portainer on my openmediavault instalation. Not sure it helps, but I placed the portainer inspect section of that image in https://pastebin.com/mwTvrUrF
Author
Owner

@ShockwaveNN commented on GitHub (May 29, 2020):

Try to remove redis mount, seems permissions on host is incorrect

<!-- gh-comment-id:635938945 --> @ShockwaveNN commented on GitHub (May 29, 2020): Try to remove redis mount, seems permissions on host is incorrect
Author
Owner

@marcoconstancio commented on GitHub (May 30, 2020):

The portainer automatically creates volumes when I don't specify any path to map in my host.

However I did try to reset/add a few more permissions on the folder where portainer keeps the container data to see if the container receives those permissions, didn't work, it contains the same permissions.

I also checked the permissions of host file on other containers and many have different permissions so I'm not sure why the docker image is different and how to change it.

<!-- gh-comment-id:636359537 --> @marcoconstancio commented on GitHub (May 30, 2020): The portainer automatically creates volumes when I don't specify any path to map in my host. However I did try to reset/add a few more permissions on the folder where portainer keeps the container data to see if the container receives those permissions, didn't work, it contains the same permissions. I also checked the permissions of host file on other containers and many have different permissions so I'm not sure why the docker image is different and how to change it.
Author
Owner

@ShockwaveNN commented on GitHub (May 30, 2020):

The portainer automatically creates volumes when I don't specify any path to map in my host.

Since we do not guarantee that we work with portainer I not really sure this is problem on our side.
Are you sure you cannot force portainer not to mount those folders?

I have no experience with portainer, so if anyone are ready to help - welcome

<!-- gh-comment-id:636375443 --> @ShockwaveNN commented on GitHub (May 30, 2020): > The portainer automatically creates volumes when I don't specify any path to map in my host. Since we do not guarantee that we work with portainer I not really sure this is problem on our side. Are you sure you cannot force portainer not to mount those folders? I have no experience with portainer, so if anyone are ready to help - welcome
Author
Owner

@ShockwaveNN commented on GitHub (Apr 29, 2021):

This issue was closed due to no response.

<!-- gh-comment-id:829085681 --> @ShockwaveNN commented on GitHub (Apr 29, 2021): This issue was closed due to no response.
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#141
No description provided.