ldap_sync_1 | thread 'main' panicked at 'Failed to open config file at /config.toml', src/config.rs:25:9 about vaultwarden_ldap HOT 6 CLOSED

There are a few different types of volumes. What you are describing name:/path is a named volume. For this type of volume, docker will create an empty directory within your docker runtime path and mount it to the destination listed within the container. In other words docker_volume_name:/destination/within/container.

In the example I linked, I am using a bind mount with a relative path. In this type of volume is described as ./local/path/relative/to/compose:/destination/within/container. The left (source) side can be an absolute path too, if you wish.

It's common to use a bind mount to bind config files from the host machine to the container. Named volumes like you're using are common for data volumes where there is really data from the outside you're trying to mount into it. You're only trying to tell Docker to keep this directory in a named volume so it persists when containers are destroyed or recreated.

Here's the Docker Compose documentation on volumes for reference.

With that background done, the spoilers on what you need to do is the following: ./config/config.toml:/config.toml.

from vaultwarden_ldap.

Ok thank you, after some searching around I found I will have to do some work on my LDAP. So closing this now.
Thanks again for your friendly help and explanation. Huge help.
I wish you a nice day 👍

from vaultwarden_ldap.

The way you're mounting config volume is incorrect.

Check out the example: https://github.com/ViViDboarder/bitwarden_rs_ldap/blob/master/docker-compose.yml#L8

from vaultwarden_ldap.

Could you give me an example with my file path please. I do not understand the Syntax in the Example. I thought volumes should be created with name:/path.
I only installed Docker for bitwardenrs, so please forgive my inexperience, I am trying to learn, as I have never seen this way of creating volumes before.

from vaultwarden_ldap.

Wow, thanks for that great explanation.

After following your advice, I am greeted with another error:
thread 'main' panicked at 'rc=1 (operationsError), dn: "", text: "00002020: Operation unavailable without authentication"', src/main.rs:22:9

Does that mean the credentials for my LDAP Login are wrong or that my login for the local bitwardenrs Server is not working ? :)

from vaultwarden_ldap.

That's a great question. The panic doesn't show very much. Are there other log messages? In most error cases, I log out some message, but there are a few in the LDAP connection that do not. In other words, if there is no other indication, I'd say it's your LDAP connection.

from vaultwarden_ldap.