-
Notifications
You must be signed in to change notification settings - Fork 241
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
Comments
found them here: |
Note that this doesn't seem to support M1/M2 MacBooks: |
Ideally this wouldn't be so hard to find. I was also using the older docker hub versions. Line 28 in 7fa1997
|
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. |
Doesn't work anymore unfortunately :( |
It still works, but you need to find a valid tag. It seems to be a few versions behind the latest release here on github. You can use skopeo to get a list of tags from a registry: With docker cli you can run this to get the list That should output something like this
Choose your tag and have fun. Good luck! |
Would be really worth to put the image location in the docs. |
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?
The text was updated successfully, but these errors were encountered: