Container is restarting with error code 132

[CountCypher]

Hi there!

I'm hosting Piped including piped-proxy in docker on RaspberryPi4. It has been running flawlessly for months, but after some recent update the piped-proxy container doesn't start anymore:

$docker compose logs -f piped-proxy
piped-proxy exited with code 132 (restarting)
piped-proxy exited with code 132 (restarting)
piped-proxy exited with code 132 (restarting)
...

Here the piped-proxy part of my docker-compose.yml:

    piped-proxy:
        image: 1337kavin/piped-proxy:latest-arm64
        restart: unless-stopped
        environment:
            - UDS=1
        volumes:
            - piped-proxy:/app/socket
        container_name: piped-proxy
        security_opt:
          - no-new-privileges:true
        labels:
          - "com.centurylinklabs.watchtower.enable=true"
          - "diun.enable=false"
  volumes:
    piped-proxy: null

Anything I can do to fix this? Happy to provide more debug info if needed.
Thanks in advance. ☺️

[NicKoehler]

I have the same issue, for now I did rollback to the previous image

[CountCypher]

I have the same issue, for now I did rollback to the previous image

@NicKoehler How can I find out the tag for the previous docker image? On Docker Hub I'm only able to find the latest tags.

[NicKoehler]

I listed all local images using:

docker image ls -a

And then guessed the correct one based on size of the current one.

mine was:

IMAGE                                                ID             DISK USAGE   CONTENT SIZE   EXTRA
...
...
...
<untagged>                                           8dd056c0e240        114MB             0B

Then I replaced the ID in the docker compose file like this:

piped-proxy:
    image: 8dd056c0e240
    # image: 1337kavin/piped-proxy:latest

[CountCypher]

Unfortunately, watchtower is pruning old docker images in my case right away after the update every night. I believe I only see the latest images present on my system:

$ docker image ls -a
                                                                                                                                                     i Info →   U  In Use
IMAGE                                       ID             DISK USAGE   CONTENT SIZE   EXTRA
1337kavin/piped-frontend:latest             3a73e668afc7         84MB             0B    U   
1337kavin/piped-proxy:latest                c6a851fbe331        114MB             0B    U   
1337kavin/piped-proxy:latest-arm64          c6a851fbe331        114MB             0B    U   
1337kavin/piped:latest                      9975d0b5b8af        413MB             0B 

Any other way to obtain a previous docker image of piped-proxy?

[NicKoehler]

try this:

piped-proxy:
    image: piped-proxy
    build: https://github.com/TeamPiped/piped-proxy.git#23b6d74d2c7aea157a36b20da6232268e472c57e

and then:

docker compose build && docker compose up -d

[WilsontheWolf]

I found this on my system. I'm running a raspberry pi 4. I ran this to run the container docker run -t -i --rm 1337kavin/piped-proxy sh. Running ./piped-proxy returns Illegal instruction (core dumped). I installed and ran it under gdb and got this (I don't really know what it means)

Ambiguous command "a": actions, add-auto-load-safe-path, add-auto-load-scripts-directory, add-inferior...
(gdb) run
Starting program: /app/piped-proxy 
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x0000aaaabdb7c718 in _mi_atomic_once_enter ()

[CountCypher]

try this:

piped-proxy:
image: piped-proxy
build: https://github.com/TeamPiped/piped-proxy.git#23b6d74d2c7aea157a36b20da6232268e472c57e

and then:

docker compose build && docker compose up -d

@NicKoehler That worked for me. Thanks a lot. ☺️

[NicKoehler]

#453 should fix this

[NicKoehler]

Tested the last image and now is working as intended.