Problems with docker installation on a formatted machine #8356
-
Hi!
However the installation by
It complains about the ownerships and the port permissions. So I've tried with
That's why I cancel the process with |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
Have you made any changes to the provided docker-compose setup file? Or using the standard one |
Beta Was this translation helpful? Give feedback.
-
Ownership Problem SolvedThis problem caused because I was getting the compose up without detach mode ( Now the only error remained is:
Looking for a solution for that too, and will update this post when I find one... |
Beta Was this translation helpful? Give feedback.
-
I 've finally gotten rid of the following problem which was causing the installation not to complete by replacing the docker compose run --rm inventree-server invoke update
[+] Running 15/15
✔ inventree-db Pulled 31.0s
✔ a480a496ba95 Pull complete 8.9s
✔ ca9f94f36076 Pull complete 10.2s
✔ d510032d6c39 Pull complete 10.9s
✔ 7e7daeb645a3 Pull complete 11.1s
✔ f38fca5434ca Pull complete 12.3s
✔ 4bc1c02e3299 Pull complete 12.5s
✔ d2b7c76e60d8 Pull complete 12.5s
✔ bb6d20b11faa Pull complete 12.6s
✔ 3dcf55f689bf Pull complete 29.4s
✔ 3ee3aebba5b4 Pull complete 29.4s
✔ d5278d8d7d46 Pull complete 29.4s
✔ ddccbe9a8e74 Pull complete 29.5s
✔ 8d0667368586 Pull complete 29.5s
✔ 53989aa24808 Pull complete 29.5s
[+] Creating 2/2
✔ Network inventree_default Created 0.1s
✔ Container inventree-db Created 0.1s
[+] Running 1/1
✔ Container inventree-db Started 0.2s
[+] Running 19/19
✔ inventree-server Pulled 82.3s
✔ 619be1103602 Pull complete 1.7s
✔ 36988be9c68b Pull complete 2.2s
✔ 46d5b401bdc2 Pull complete 4.1s
✔ 4e0054417e48 Pull complete 4.2s
✔ 47f039281c77 Pull complete 4.9s
✔ 377eb0a02c4b Pull complete 59.6s
✔ a87ef38f81e2 Pull complete 59.7s
✔ 4f4fb700ef54 Pull complete 59.7s
✔ ebac38604b55 Pull complete 59.7s
✔ f4f4f9343cbb Pull complete 59.7s
✔ 3d90614e3e3f Pull complete 59.8s
✔ 4453a6a16630 Pull complete 59.8s
✔ e6f79c261b1e Pull complete 59.9s
✔ 2bc51070dc58 Pull complete 59.9s
✔ b99ab66de85d Pull complete 74.9s
✔ 3276268bf0aa Pull complete 79.7s
✔ 448e204f7b34 Pull complete 79.7s
✔ 14700720b7a1 Pull complete 80.1s
Creating directory /home/inventree/data/static
Creating directory /home/inventree/data/media
Creating directory
BusyBox v1.36.1 (2023-11-06 11:32:24 UTC) multi-call binary.
Usage: mkdir [-m MODE] [-p] DIRECTORY...
Create DIRECTORY
-m MODE Mode
-p No error if exists; make parent directories as needed Then I deleted all images of inventree and reinstalled and up using the following sequence: docker compose run --rm inventree-server invoke update
docker compose up -d PS: Since this is a reinstallation on an existing inventree installation, I skipped the database admin creation step. Finally I've got inventree running at http://inventree.localhost/ and displaying the login screen. However this time I can't login with the existed users I had from previous installation (1 admin and 1 user). I use the correct credentials for both but always get the following screen: None of those accounts was set a recovery email so I followed the steps described in this page -> https://docs.inventree.org/en/stable/start/accounts/?h=recover#reset-password-via-command-line. I managed to change the passwords successfully for each user: docker exec -it inventree-server python src/backend/InvenTree/manage.py changepassword ismail
Python version 3.11.9 - /usr/local/bin/python
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Changing password for user 'ismail'
Password:
Password (again):
Password changed successfully for user 'ismail' docker exec -it inventree-server python src/backend/InvenTree/manage.py changepassword admin-ismail
Python version 3.11.9 - /usr/local/bin/python
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Changing password for user 'admin-ismail'
Password:
Password (again):
Password changed successfully for user 'admin-ismail' Then I restarted all containers with
@SchrodingersGat do you know any remedy for this? I appreciate your time and help. |
Beta Was this translation helpful? Give feedback.
-
@kozmotronik take a look at the 0.16.7 release notes - I recently fixed a login bug which I think might be what is going wrong for you now Please note there is a breaking change for your configuration you will need to change the value of |
Beta Was this translation helpful? Give feedback.
Yes sir! That was it. Although I don't use SSO feature (it is disabled) this solves the login issue. But I took the long way to do it:
INVENTREE_TAG
fromstable
tolatest
0.17.0
(development version)INVENTREE_TAG
back tostable
0.16.7
Thank you very much!