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

Docker image and version confusion #4986

Open
ferbs opened this issue Jan 29, 2023 · 4 comments
Open

Docker image and version confusion #4986

ferbs opened this issue Jan 29, 2023 · 4 comments

Comments

@ferbs
Copy link

ferbs commented Jan 29, 2023

Is docker hub the right repository to use for this project?

Old versions have been pushed to the repo after newer versions, such that the first page mainly shows only v7 releases. (eg zenko/cloudserver:latest-7.10.19) And it's missing newer versions deeper in--the newest there is :8.2.7 but Github Releases shows @zenko/cloudserver is actually up to v8.7.7. Also, the value for "version" in package.json is inconsistent, showing v8.1.2 for that v8.2.7 image.

(I'm glad I noticed a v8 image because v7 bugs were getting frustrating: docker-entrypoint.sh fails to split the ENDPOINTS environment variable and it also clobbers any bind-mounted config file at /usr/src/app/config.json)

How to find the latest?

@b091
Copy link

b091 commented Jun 5, 2023

found them here: registry.scality.com/cloudserver/cloudserver:8.7.23 ;)

@c-w
Copy link

c-w commented Jun 18, 2023

found them here: registry.scality.com/cloudserver/cloudserver:8.7.23 ;)

Note that this doesn't seem to support M1/M2 MacBooks: no matching manifest for linux/arm64/v8 in the manifest list entries

@ndtreviv
Copy link

Ideally this wouldn't be so hard to find. I was also using the older docker hub versions.
In fact, even the README takes you to the wrong place:

[Run your Zenko CloudServer with Docker](https://hub.docker.com/r/zenko/cloudserver/)

@ferbs
Copy link
Author

ferbs commented Apr 26, 2024

Also related to inconsistent versioning, there are many dynamic dependencies in package dependencies that use named git tags. If using url-based dependencies over published packages at all, it's safer to use its sha commit, not a named tag that might silently change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants