-
Notifications
You must be signed in to change notification settings - Fork 52
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
Update dev docs on how to run via docker #692
Comments
@dcmcand I believe this was recently addressed - though it might have been on the conda-stor-ui side of things only. |
Note: I did check the doc file when I reported this, so it's just necessary to make the suggested change. UPD: The docs were recently moved, please check all files under |
@nkaretnikov I can't reproduce this. From the main branch running |
@dcmcand I cannot double-check right now, but before I forget: could it be due to a different version of docker compose being used? Note how the docs say "docker-compose", with a dash. On my machine, these are two different tools:
The one with the dash is installed via conda. |
I actually tried both to be sure and they both worked for me.
…On Fri, Dec 22, 2023, 5:02 PM Nikita Karetnikov ***@***.***> wrote:
@dcmcand <https://github.com/dcmcand> I cannot double-check right now,
but before I forget: could it be due to a different version of docker
compose being used? Note how the docs say "docker-compose", with a dash.
On my machine, these are two different tools:
$ docker-compose --version
docker-compose version 1.29.2, build unknown
$ docker compose --version
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
—
Reply to this email directly, view it on GitHub
<#692 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPVTRZP4MMCRW3DVFYQQF3YKX7O5AVCNFSM6AAAAABAO32D6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGA4TMMZQG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dcmcand Could you post the version numbers of both tools on your machine? I'll compare to what I have locally. |
docker compose version v2.21.0 |
@dcmcand I've just tried it again in a new env, still fails. Full log attached. Any idea what might be wrong here?
Versions:
|
Nevermind, after I posted the above, I saw:
So I went ahead and re-installed Docker Desktop and Docker Engine as specified in: Now |
Context
Because
RELEASE_VERSION
was added in #621, the following command fromdocs/contributing.md
no longer works:Note: there are multiple places in the file where this command is mentioned - update all of them.
Instead, this is what seems to work locally:
docker-compose build --build-arg RELEASE_VERSION=2023.10.1 && docker-compose up
I don't think
RELEASE_VERSION
matters much because later in Dockerfile it just installs from the current dir:Note that this works fine on GitHub as is because there's an additional step that sets
RELEASE_VERSION
:RELEASE_VERSION=${{github.ref_name}}
Value and/or benefit
Instructions are valid and tell how to start the server via docker for local dev.
Anything else?
No response
The text was updated successfully, but these errors were encountered: