mirror of
https://github.com/minoplhy/docker-ripe-atlas.git
synced 2025-04-21 12:26:59 +00:00
revert base image to Debian 10 per https://github.com/Jamesits/docker-ripe-atlas/issues/19
This commit is contained in:
parent
88494cd15f
commit
8060f65f1a
@ -1,5 +1,5 @@
|
||||
## builder
|
||||
FROM --platform=$BUILDPLATFORM debian:stable-slim as builder
|
||||
FROM --platform=$BUILDPLATFORM debian:10-slim as builder
|
||||
LABEL image="ripe-atlas-builder"
|
||||
ARG BUILDPLATFORM
|
||||
ARG TARGETPLATFORM
|
||||
|
12
README.md
12
README.md
@ -126,15 +126,3 @@ Then start the RIPE Atlas container with argument `--label=com.centurylinklabs.w
|
||||
### Backup
|
||||
|
||||
All the config files are stored at `/var/atlas-probe`. Just backup it.
|
||||
|
||||
### `sleep` command not working
|
||||
|
||||
On some systems, syscall `clock_nanosleep` and `clock_nanosleep_time64` are blocked by the default Docker seccomp.
|
||||
|
||||
Symptoms:
|
||||
- During container startup, `WARNING: clock_nanosleep or clock_nanosleep_time64 is not available on the system` is printed
|
||||
- Atlas software stops working after a while, printing logs like `sleep: cannot read realtime clock: Operation not permitted`
|
||||
|
||||
Temporary workaround:
|
||||
|
||||
Add `--security-opt seccomp:unconfined` to the `docker run` commandline.
|
||||
|
Loading…
x
Reference in New Issue
Block a user