I’m a bit stuck in the getting started guide at the following point:
FROM balenalib/%%BALENA_MACHINE_NAME%%-alpine
CMD [ "balena-idle" ]
balena deploy myApp --logs
I cannot get balena to push the image to the registry, it keeps trying and then fails after 3 tries.
I then took a look at the logs of the registry, and i always see the following lines:
Jul 26 15:07:05 43e54771f23a registry[1211]: time=“2022-07-26T15:07:05.878061021Z” level=error msg=“response completed with error” auth.user.name=admin err.code=unknown err.detail="s3aws: InvalidAccessKeyId: The Access Key Id you provided does not exist in our records.
Any solution to this? My understanding is that by default, openBalena uses Minio storage and not s3aws. I don’t seem to see where to change to use the local s3 container as a server. Please help!
Openbalena uses Minio as a standard S3 provider. S3 is from AWS and that’s why the error indicates it uses AWS, but instead it uses the Minio instance provided by open-balena-s3. But maybe you knew that already!
It looks like the registry can’t connect with the right credentials to the Minio server. I can’t debug your instance, but what I can do is spin up my own instance and try if I can replicate the issue. So give me some time and I’ll report back here!
Hey
That would be great, I already spun up a second Openbalena on a different Server and Hypervisor with the same results. But it would certainly help if someone with more knowledge on the subject would try it as well and maybe find a solution
So I’ve tested it and replicated the problem.
The problem seems to lie in the fact that Minio has changed something in the latest releases, which breaks the open-balena-s3 container. However, it seems like that is fixed in v2.13.9, which pins the Minio release.
So my suggestion would be to upgrade the container to the latest version. I’ll also create a PR that does this for the open-balena repository, so you can wait for that or change the version in the compose/versions file manually for the time being.
Please let me know if this helps!
Maybe you should remove the S3 volume, but try to upgrade first!
Hey
Thanks for debugging and resolving the issue. I had to remove the S3 volume, only upgrading didn’t quite do the trick. After removing the S3 volume and restarting compose everything worked as expected.
