-
Notifications
You must be signed in to change notification settings - Fork 41
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 compose doesn't pass cli arguments #65
Comments
hmm so afaik this help page only appears if no arguments are passed or the otherwise it should look like this, even if only the
You're command looks correct though, but i'm not that familiar with docker compose |
@zeratax |
weird is the following message from logs
first claims wrong (missing) params then claiming command does not exist at all??? |
regarding the image: I should have used
so my command doubled ;-) I'd recommend to remove the --config-path from entrypoint or else it cannot be specified via cli in command.
currently back to 0.8.0 from pip, will try again the latest version and fix the config later today |
okay it works now with latest version from pip. Had to change
|
it will use the last provided --config-path. so you should be able to just overwrite it |
if I try it with your image and overwrite with the following command
I still get
but anyway that's okay with me as I just can use the latest version from pip and with that it works as expected |
no I mean can't you just do: "Cmd": [
"--config-path",
"/etc/config.yaml",
"serve"
], that should result in: $ /nix/store/y611r8b86zv0l2r2xnlf408j718f62xl-python3.8-matrix-registration/bin/matrix-registration \
--config-path /data/config.yaml \
--config-path /etc/config.yaml \
serve where only the last |
@zeratax
but then it throws exceptions that the db cannot be opened
guess it tries the /data path to find the db (from first --config-path) |
it definitely shouldn't. the db is handled like everything else: $ grep db configA.yaml
db: 'sqlite:///{cwd}dbA.sqlite3'
$ grep db configB.yaml
db: 'sqlite:///{cwd}dbB.sqlite3'
$ matrix-registration --config-path=configA.yaml --config-path=configB.yaml generate
UserColonyTaboo
$ ls db*
dbB.sqlite3 Here the first Are you sure there isn't just a mistake with your config file? sqlalchemy expects an absolute path, so if you want to do a relative path it should look like this db: 'sqlite:///{cwd}db.sqlite3' where cwd will be replaced by the current working directory |
I have the following three mounts in my docker-compose
and config.yaml defines db as |
okay sorry the documentation here is wrong and idk how I didn't notice this earlier, but the config file is read in the docker environment so the db isn't in so it should be: db: 'sqlite:////data/db.sqlite3' |
@zeratax |
since i can't reproduce this at all and you seem to have found a solution I'll consider this fixed until someone says otherwise ^^ |
sorry to re-open this issue. But now seems that the version on pip updated as well. So I got my version updated today and it produces the same errors (regardless of pip or docker image directly)
my command in docker-compose looks like this
so atm matrix-registration is completly broken for me
The only way that works for me is to change my Dockerfile for the build to install
matrix-registration==0.8.0
from pipOriginally posted by @jahlives in #64 (comment)
The text was updated successfully, but these errors were encountered: