uptime-kuma: Docker 1.0.3 restarting / error (ARMv7 only)
After pulling the latest docker build, the docker instance wont start and is stuck in a constant restarting loop.
The following command to see whats going on:
sudo docker logs --tail 20 --follow --timestamps containername
Results in:
2021-07-14T07:06:53.133558809Z #FailureMessage Object: 0xbeb5c24c
2021-07-14T07:07:54.433098117Z
2021-07-14T07:07:54.433180876Z
2021-07-14T07:07:54.433206784Z #
2021-07-14T07:07:54.433230784Z # Fatal error in , line 0
2021-07-14T07:07:54.433253876Z # unreachable code
2021-07-14T07:07:54.433276913Z #
2021-07-14T07:07:54.433299580Z #
2021-07-14T07:07:54.433322394Z #
2021-07-14T07:07:54.433345006Z #FailureMessage Object: 0xbeb3424c
2021-07-14T07:08:55.696356724Z
2021-07-14T07:08:55.696458391Z
2021-07-14T07:08:55.696482409Z #
2021-07-14T07:08:55.696504279Z # Fatal error in , line 0
2021-07-14T07:08:55.696525650Z # unreachable code
2021-07-14T07:08:55.696546816Z #
2021-07-14T07:08:55.696567557Z #
2021-07-14T07:08:55.696588168Z #
2021-07-14T07:08:55.696608686Z #FailureMessage Object: 0xbe9a224c
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (12 by maintainers)
@louislam FYI this issue isn’t going to go away unless someone updates libseccomp2 in the main repo for Debian armv7 (it can also be caused by people running old versions of the Docker engine).
The “fix” is client-side - update libseccomp from the Buster Backports repo and make sure the docker engine is up to date from their repos rather than the distro repos which are frequently way behind. Alpine 3.13 (and indeed 3.14) based build of your image works fine on a patched armv7 Rasbian/Pi OS host.
with docker is not possible, base nodejs image do not provide armv6. without docker maybe possible.