You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've noticed that if I run something like this:
invenio users create -a --password mysupersecretpw [email protected] --confirm;
The user is created and login works, if the command runs inside web container
The user is created and login fails (invalid password), if the command runs inside worker container
However, README.md says to bootstrap invenio launching setup.sh (which contains varied invenio statements) inside worker container but, at the sime time, other monolithic invenio operations should be run inside web container (for example docker exec -it invenio-rdm-starter-web-1 invenio rdm-records add-to-fixture affiliations). Web and worker use the same docker image and the difference seems to rely on the CMD statement.
What is a good practice to understand which is the right container if you need to run invenio cli operations?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've noticed that if I run something like this:
However,
README.md
says to bootstrap invenio launchingsetup.sh
(which contains variedinvenio
statements) inside worker container but, at the sime time, other monolithicinvenio
operations should be run inside web container (for exampledocker exec -it invenio-rdm-starter-web-1 invenio rdm-records add-to-fixture affiliations
).Web and worker use the same docker image and the difference seems to rely on the CMD statement.
What is a good practice to understand which is the right container if you need to run invenio cli operations?
Thank you very much
Beta Was this translation helpful? Give feedback.
All reactions