Hemanth Bollamreddi

I do not exactly get unauthorized like in the issue mentioned. The browser does not return anything.

Hey ! @guillaumedsde thanks for all this info. I need some time to test these changes. Will get back once done.

Thanks for the quick reply @towe75 I think the rootless bug is fixed in master and can be marked resolved.  --- > Regarding the socket path: yeah, we could...

The error is as follows on nomad: ``` 2021-06-05T20:48:53.882+0530 [ERROR] client.rpc: error performing RPC to server: error="RPC Error:: 400,ACL support disabled" rpc=ACL.ResolveToken server=xx.xx.xx.xx:4647 2021-06-05T20:48:53.883+0530 [ERROR] client.rpc: error performing RPC to...

Just ran koel on docker and was **NOT** able to login without running the `init` command. But it is said the default user/pass would work. Any help here please ?

Hi @Hyzual thanks for the clarification. I was wondering if it is possible to automate this, say, by adding the command in Dockerfile itself instead of user needing to manually...

Hey ! Thanks for the effort @Hyzual ! I remember seeing a similar issue elsewhere... I think they got around it by using some kind of bash script which waits...

Here are some which people tend to use. 1. https://github.com/vishnubob/wait-for-it (Docker: https://github.com/whs/docker-wait-for-it) 2. https://github.com/palfrey/wait-for-db 3. https://github.com/eficode/wait-for 4. https://github.com/nickjj/wait-until 5. https://github.com/ufoscout/docker-compose-wait

Hi @shoenig, added a prior art in the post. It uses a somewhat similar mechanism of using existing periodic job type.

Would love to know your impl details, if possible. Do you use `exec` or `raw_exec` drivers ?