Hi everyone, is there a reason that the latest tag for the docker image does not have an arm64 image? I can build it however it would be easier to pull it from dockerhub. I use ipfs-cluster on Raspberry pi..
Thanks!
Not sure why that is exactly. However, I would recommend you to use the latest release tag which is stable and points to v1.1.2
Thanks for the hint!
For the stable image we got this on two different raspberry pi installations, therefore we built the docker image from latest:
cluster0 | /usr/local/bin/ipfs-cluster-service: line 12: syntax error: unterminated quoted string cluster0 exited with code 2
Can you try the master-latest tag: https://hub.docker.com/layers/ipfs/ipfs-cluster/master-latest/images/sha256-925e5a90c87e3a804a435a20f5e477a3b149a4ee172d646d06f53ec370fc4019
It might be already fixed in main but just not released.
If not, could you please open an issue in the repo GitHub · Where software is built
1 Like
This happens when starting the container? Or when?
Yes exactly. If the image is built from the Dockerfile it seems to work fine.
Ah so you have something custom based the official container?
The start script does ipfs-cluster-ctl ls or id. It might be that is breaking when it sees a multiaddress that it cannot parse. Did you add something custom there?
Or if you mean it works by manually building but not the prebuilt image, then I’m not sure. I cannot look right now but might be a bug..
Sorry, yes this is what I meant. Pulling the image results in an error when starting on Raspi/arm64. Cloning the repo and then building using the Dockerfile works fine.
With stable or v1.1.2, I get the following error:
# docker-compose logs -- cluster0
cluster0 | Changing user to ipfs
cluster0 | /usr/local/bin/ipfs-cluster-service: line 1: syntax error: unexpected "("
I have tried cloning the git, and build my own image with the tag v1.1.2.
I am getting the following error now:
error applying environment variables to configuration: error loading cluster secret from config: encoding/hex: invalid byte: U+004D 'M'
Generating the CLUSTER_SECRET or leaving it unset results in a similar error.
During CI, it is verified that the Docker container builds and starts fine so i would take a closer look at your setup.
The idea of docker is to simplify deployment and insure full compatibility. Did you check for aarch64/arm64?
The original issue here (latest tag missing) was fixed docker/entrypoint.sh calls `su-exec`, but image does not contain `su-exec` in PATH · Issue #2133 · ipfs-cluster/ipfs-cluster · GitHub but we haven’t had a release since then. I believe I can do it next week.