readonly/docker-ripe-atlas
1
0
Fork 0
mirror of https://github.com/minoplhy/docker-ripe-atlas.git synced 2025-04-21 20:36:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

revert base image to Debian 10 per https://github.com/Jamesits/docker-ripe-atlas/issues/19

Browse Source
This commit is contained in:
James Swineson 2022-05-15 18:30:16 +08:00 committed by GitHub
parent 88494cd15f
commit 8060f65f1a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 1 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Dockerfile
View File

@ -1,5 +1,5 @@
## builder ## builder
FROM --platform=$BUILDPLATFORM debian:stable-slim as builder FROM --platform=$BUILDPLATFORM debian:10-slim as builder
LABEL image="ripe-atlas-builder" LABEL image="ripe-atlas-builder"
ARG BUILDPLATFORM ARG BUILDPLATFORM
ARG TARGETPLATFORM ARG TARGETPLATFORM

12
README.md
View File

@ -126,15 +126,3 @@ Then start the RIPE Atlas container with argument `--label=com.centurylinklabs.w
### Backup ### Backup
All the config files are stored at `/var/atlas-probe`. Just backup it. 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.