Open mybuntu-git2 opened 6 months ago
Hi!
auth-bearer
service? I doubt that this is possible.Hi micbar, Thanks for your reply. Update from 4.0.2 to 4.0.6 to 5.0.0 The goal of OCIS_EXCLUDE_RUN_SERVICES was to remove “things that I do not need” as I want to minimise resource consumption The auth-bearer is indeed disabled for that reason
Hi @mybuntu-git2
In general you a right, ocis should work without the services you excluded. I can run it fine locally without.
Here something goes utterly wrong during login. Can you try disabling the redis
cache and retry? I can see a cache hit
log just before things go downward. Maybe something is stuck in there that doesn't play well with 5.0
.
Additional info: ocis5 uses the included natsjs
as cache, so if you want to save resources you do not need to run redis
any more.
Hi, Thanks again for your help. Commented out the redis setup and re-enabled ocm and auth-bearer.
now I get
{"level":"fatal","service":"nats","time":"2024-03-28T13:00:12Z"
,"line":"github.com/owncloud/ocis/v2/services/nats/pkg/logging/
nats.go:33","message":"Can't start JetStream: storage directory is not a directory"}
I guess this could be an ownership issue and have 2 questions:
I guess this could be an ownership issue and have 2 questions:
- where is the folder tree/file in question to which I can change ownership and execution ?
- In previous versions the user variable in docker_compose was not taking effect (I was trying 0:0) and it was still needed to have the folders passed to the container, owned by 1000:1000. do you know if that now works, do you experience the same problem?
Ocis uses user:group 1000:1000 in the container to run "root-less"
Your docker-compose shows that the ocis data directory uses a bind mount data_symlink
. This needs to be writable by the ocis process.
Describe the bug
owncloud docker v5.0.0 on arm Login does not work for previously working user and password
Steps to reproduce
Not logged in This could be because of a routine safety log out, or because your account is either inactive or not yet authorized for use. Please try logging in after a while or seek help from your Administrator
Expected behavior
Login should happen
Actual behavior
Return message at repro step 3 and login does not happen (see details for debug log)
Setup
Docker v5.0.0 docker-compose.yml:
Additional context
Add any other context about the problem here.