mollyim / mollysocket

MollySocket allows getting Signal notifications via UnifiedPush.
GNU Affero General Public License v3.0
110 stars 10 forks source link

1.3.0 docker image release seems to be only armv7 #32

Closed pjv closed 8 months ago

pjv commented 8 months ago

I tried updating my mollysocket docker-compose based install and mollysocket wouldn’t start after pulling latest.

I saw this error on the command line when trying to bring up the container:

mollysocket The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested 0.0s
canceled

Then I looked at the releases listed here: https://ghcr.io/mollyim/mollysocket and it looks like prior releases have 4 architectures available but the latest (1.3.0) doesn’t have an Arch tab on its release details…

SCR-20240324-jpca SCR-20240324-jphx
p1gp1g commented 8 months ago

Thanks, the github CI env was broken yesterday and I had to run it again for arm7 only. I'm running the CI again :+1:

againstpetra commented 8 months ago

even after the re-run, it still looks broken for me:

docker: image with reference ghcr.io/mollyim/mollysocket:1.3.0 was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64.

and the page in ghcr still doesn't show an os/arch page

pjv commented 8 months ago

and the page in ghcr still doesn't show an os/arch page

yup.

notdeadyett commented 8 months ago

I'm having the same problem. I had to revet back to 1.2 for now.

p1gp1g commented 8 months ago

I know, I have removed the tag to run it again, maybe I'll split the container to another tag for arm7, it freezes again.

If you have the issue, subscribe to this issue, you will be notified when it is fixed

pjv commented 8 months ago

The build for the architecture I’m missing seems to be completing successfully. Most recent run this morning:

SCR-20240325-hfqx

Somehow though, that build artifact doesn’t seem to be going where it needs to.

p1gp1g commented 8 months ago

That is fixed now, I'll improve the CI for the next release