Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[suitecrm]: tag 8.7.0 does not appear to include 8.7.0 sources ... ? #73179

Open
JoshMcCullough opened this issue Oct 8, 2024 · 2 comments
Open
Assignees
Labels
tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@JoshMcCullough
Copy link

JoshMcCullough commented Oct 8, 2024

Name and Version

bitnami/suitecrm:8.7.0

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Run the container and exec into it.
  2. cat /bitnami/suitecrm/public/legacy/suitecrm_version.php --> shows version 8.6.0
  3. env | grep 8. --> shows `8.7.0

Update: the file at /opt/bitnami/suitecrm/public/legacy/suitecrm_version.php does include the correct version.

What is the expected behavior?

Version information should match that of the release. Unclear if the 8.7.0 tag is actually 8.7.0 or 8.6.0.

What do you see instead?

Version information shows both versions.

Additional information

No response

@JoshMcCullough JoshMcCullough added the tech-issues The user has a technical issue about an application label Oct 8, 2024
@github-actions github-actions bot added the triage Triage is needed label Oct 8, 2024
@JoshMcCullough
Copy link
Author

Our host dir /data/docker/volumes/suitecrm_data/_data is mapped to the container dir /bitnami/suitecrm. This dir is the one that appears to contain the 8.6.0 sources. On the container itself (when running without the volume), the current/correct sources are within /opt/bitnami/suitecrm.

On our running instance, /opt/bitnami/suitecrm is a symlink to /bitnami/suitecrm (the mapped volume).

Could this be caused by the persistence feature of this image?

@JoshMcCullough
Copy link
Author

Regarding the above, indeed, it appears that if I run version A, then those sources are persisted to to the mapped volume. If I then replace version A with version B, the original version A sources are restored over version B's sources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants