Update to new Evolution API image source and pin it to the latest version#644
Update to new Evolution API image source and pin it to the latest version#644matheusfelipeog wants to merge 1 commit intoDokploy:canaryfrom
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
There was a problem hiding this comment.
Pull request overview
This PR updates the Evolution API Docker image source from the deprecated atendai/evolution-api to the new official location evoapicloud/evolution-api. The change addresses issues #428 and #430, where the old v2.1.2 version contained vulnerabilities and didn't work correctly.
Key Changes:
- Updates Docker image source from
atendai/evolution-api:v2.1.2toevoapicloud/evolution-api:latest
| services: | ||
| evolution-api: | ||
| image: atendai/evolution-api:v2.1.2 | ||
| image: evoapicloud/evolution-api:latest |
There was a problem hiding this comment.
Using the latest tag violates project conventions. According to the project guidelines, images must be pinned to specific versions in docker-compose.yml. The latest tag should never be used as it can break templates when upstream images change unexpectedly.
Please update this to a specific version tag (e.g., evoapicloud/evolution-api:v2.2.0 or whatever the current stable version is). You should verify the image exists using docker manifest inspect evoapicloud/evolution-api:<version> before committing.
There was a problem hiding this comment.
Just a comment on this:
I don’t agree with pinning a fixed version for the Evolution API template, because features frequently stop working correctly due to updates in projects that Evolution API depends on (WhatsApp, Baileys, etc). That would mean we would constantly need to update the template version here so others don’t end up using something broken, vulnerable, or outdated. Not to mention the creation of issues assuming it’s a Dokploy problem, when in fact it’s caused by the pinned version.
By pinning the version to latest, we ensure that a functional and theoretically secure version is being used by users.
There was a problem hiding this comment.
In any case, if it would be ideal to use the latest version, shouldn't other versions exist because they wouldn't work? @matheusfelipeog
There was a problem hiding this comment.
@Siumauricio, that’s a valid question, but I’m not a maintainer of the EvolutionAPI project and I don’t have insight into the motivations behind their internal decisions.
I believe the main point is that, for the core feature at the moment, older versions simply don’t work. In fact, whenever there’s some kind of issue related to this core feature, the guidance is almost always something like, “Update to the latest version.”
The Evolution API Docker image is no longer located at atendai/evolution-api. It is now located at evoapicloud/evolution-api.
The currently pinned version is v2.1.2. This version does not work correctly and contains vulnerabilities that have already been fixed in more recent versions.
I updated the image to the new source and pinned the version to latest.
closes #428 #430
related: