docker-vernemq: New version 1.12.1 results in /lib/env.sh: No such file or directory

I’ve now manually uploaded local builds for 1.12.1 and 1.12.1-alpine. Could you guys give them a test, regarding original issue? https://hub.docker.com/repository/docker/vernemq/vernemq/tags?page=1&ordering=last_updated

Thanks!

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq 👉 Using the binary VerneMQ packages (.deb/.rpm/Docker) requires a subscription.

The issue is fully identified. The Docker images pull the tarballs from the release binaries here on Github. Due to a patch to adjust the correct paths on .deb and .rpm packages, the tarballs had wrong internal paths set, making the Docker images unusuable.

New images should be up soon, but please bear with me, it’s more work than it might sound like.

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq 👉 Using the binary VerneMQ packages (.deb/.rpm/Docker) requires a subscription.

@JeremyTheocharis Deployed our stack with 1.12.1, vernemq starts successfully.

I will try it tomorrow ! Thanks for your quick action !

Hi @ioolkos,

Both 1.12.1 and 1.12.1-alpine is failing. Something is wrong with the latest VerneMQ binary. Replacing it with version 1.12.0 fixed the issue.

Error log:

/vernemq/bin/vernemq: line 8: /lib/env.sh: No such file or directory
/vernemq/bin/vernemq: line 140: check_user_internal: command not found
/vernemq/bin/vernemq: line 144: create_pid_dir: command not found
/vernemq/bin/vernemq: line 147: echoerr: command not found

@JeremyTheocharis thanks, ugh, that’s bad. I was thinking I had this fixed. It’s a path issue. I need to investigate.

EDIT: With what package from Dockerhub is this happening exactly?