Redis Container doesn't start

Community Containers
1

Hello,

I’m using Greenbone Community Container Edition with Docker on Ubuntu 22.04 LTS and continuing the discussion from /var/lib/docker/overlay2 eating up all disk space:

After freeing back the disk space, the container ‘redis-server’ can’t start.

It seems that running out of disk space seems to have broken something with the redis container …
The redis-container is permanently restarting and I can the following in the logs:

redis-server_1         | 8:C 21 Jun 2023 15:12:06.911 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-server_1         | 8:C 21 Jun 2023 15:12:06.911 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=8, just started
redis-server_1         | 8:C 21 Jun 2023 15:12:06.911 # Configuration loaded
redis-server_1         | 8:M 21 Jun 2023 15:12:06.912 * monotonic clock: POSIX clock_gettime
redis-server_1         | 8:M 21 Jun 2023 15:12:06.912 # Failed opening Unix socket: bind: Permission denied

How to fix this?

Thanks in advance.

1 Like
2

You need to stop the containers and afterwards delete the redis socket volume

docker volume rm greenbone-community-edition_redis_socket_vol

The volume will be re-created on the next start via docker compose.

2 Likes
3

@bricks Thanks for this.
It turned out that not the missing diskspace was causing this issue.
Instead it occured after updating/pulling the containers.
But after bringing all containers down and doing the mentioned command in your last post solved it …

3 Likes