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

Running on arm #272

Closed
AuspeXeu opened this issue Mar 5, 2021 · 5 comments
Closed

Running on arm #272

AuspeXeu opened this issue Mar 5, 2021 · 5 comments

Comments

@AuspeXeu
Copy link

AuspeXeu commented Mar 5, 2021

I am currently using the redis:6.0-alpine tag to run redis on my raspberry pi. This all works fine. However, when switching to redis:6.2-alpine. The container keeps crashing with this error.

redis       | 1:C 10 Jun 2037 05:58:32.000 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis       | 1:C 10 Jun 2037 05:58:32.000 # Redis version=6.2.1, bits=32, commit=00000000, modified=0, pid=1, just started
redis       | 1:C 10 Jun 2037 05:58:32.000 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis       | Assertion failed: rc == 0 (monotonic.c: monotonicInit_posix: 149)
redis       | 
redis       | 
redis       | === REDIS BUG REPORT START: Cut & paste starting from here ===
redis       | 1:M 10 Jun 2037 05:38:16.000 # Redis 6.2.1 crashed by signal: 6, si_code: -6
redis       | 1:M 10 Jun 2037 05:38:16.000 # Killed by PID: 1, UID: 999
redis       | 
redis       | ------ INFO OUTPUT ------
redis       | 1:M 10 Jun 2037 04:54:16.000 # Redis 6.2.1 crashed by signal: 11, si_code: 1
redis       | 1:M 10 Jun 2037 04:54:16.000 # Accessing address: 0x14
redis       | 1:M 10 Jun 2037 04:54:16.000 # Killed by PID: 20, UID: 0
@yosifkit
Copy link
Contributor

yosifkit commented Mar 5, 2021

Just a hunch, but this seems like moby/moby#40734 (#269 (comment)).

@ushachar
Copy link
Collaborator

ushachar commented Mar 6, 2021

This is caused by a change in Redis - redis/redis#7644
I've notified the relevant folks on that PR.

@yossigo
Copy link
Member

yossigo commented Mar 7, 2021

Looks like this is not directly related to Redis, but a Docker/libseccomp issue that causes clock_gettime() to fail. Please see alpinelinux/docker-alpine#135 for a discussion.

@tianon
Copy link
Contributor

tianon commented Mar 8, 2021

Indeed, see also https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#time64_requirements.

You need to update libseccomp on your host to 2.4.2 or newer and Docker to 19.03.9 or newer (see moby/moby#40734). 👍

@YuriyTigiev

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants