docker inspect shows that its not actually picking up my changed value. It does pick up the value PASSBOLT_SSL_FORCE=false though so it is definitely reading my env file.
I have a few questions about the docker compose version as I have it up and running now.
It tells me that it will periodically delete my data, is this correct?
It looks like soime of the options such as setting a key expiry are also greyed out. I guess what I need to know is can I use the docker compose version or will does it have restricted features and will it delete all of my passwords that I enter, and if so when, and will I get any warning?
Unfortunately we don’t have a public slack channel
If you haven’t set persistency for the mysql container your database will be wiped every time you restart the mysql container. docker-composer.yml provided comes already with persistency enabled for mysql container.
It also persists the gpg key. Some other directories such as avatars directory are persisted on this docker-compose.
With this in mind your passwords won’t be deleted upon container restarts unless your docker volumes are deleted manually from the host.
If your gpg server key expires you should create a new one and perform an account recovery. There is another thread on this forum that discusses that situation. However, by default passbolt_docker image creates a serverkey that never expires (PASSBOLT_KEY_EXPIRATION) so you likely won’t be in the previously mentioned situation.
@diego thanks for the replies, looks like a very nice tool so far!
I am mounting the folders inside the container to an EBS volume so they should persist inbetween restarts of the containers and be backed up as well so I think this should be ok.
I was worried it might be a time based limit enforced because the application was in evaluation mode but I think this clears it all up.