Overview: Support for Docker image Bicho

Application Name: Bichon
Application:  https://github.com/rustmailer/bichon

Summary :

Bichon is an open-source email archiving system that synchronizes emails from IMAP servers, indexes them for full-text search, and provides a REST API for programmatic access. Unlike email clients, Bichon is designed for archiving and searching rather than sending/receiving emails. It runs as a standalone server application that continuously synchronizes configured email accounts and maintains a searchable local archive. Built in Rust, it requires no external dependencies and provides fast, efficient email archiving, management, and search through a built-in WebUI.

 

Make sure to look at the complete documentation

Reserved

Hi, please update the default credentials in the docker template to admin // admin@bichon found in the documentation: https://github.com/rustmailer/bichon

Starting from Bichon v0.2.0, the authentication model has been updated.

Built-in Admin User (v0.2.0+)

• Bichon no longer uses the legacy single-account root / root login.

• The system now ships with a built-in admin user by default.

• Default credentials:

  • Username: admin

  • Password: admin@bichon

Hi @chickenmilk-icebright
thanks for the update , i will look at it and update .

EDIT: Updated ...

Edited January 3Jan 3 by ZappyZap

I don't know if you are still supporting this, but the latest 2.0.0-alpha1 version requires manual storage migration. The docker will automatically upgrade but will not function properly. I just gave up and rolled back to the 1.6.2 version until I have time to figure out how to do the upgrade properly.

Yes
i will check this and get back

EDIT : seem to be a bug , check https://github.com/rustmailer/bichon/issues/331
there is various way to workaround , i am evaluating the best for unraid, until the dev fix that

Edited July 31Jul 31 by ZappyZap

temporary solution :
https://github.com/rustmailer/bichon/issues/331#issuecomment-5140140687

Note: i have open a issue with dev

Thanks for looking into it. I'll give the temporary solution a try when I get a chance.

process is to add

tail -f /dev/null

to your "Extra Parameters" after toggling Advanced in edit container.

Then container will stay running, so you can then run:

bichon-admin

and select the v1 to v2 migration. I entered

/data

for the root dir, and empty for the next two as they did not apply for me (based on my env vars i was only using this one)

Then I selected 5000 (2GB RAM) in the interactive script. Note that if you take too long the script seems to time out and close the console. you can start this again, seems to cause no issue.

it was done very quickly (less than 1min), but i don't have a huge amount of email.

Then edit the container again to remove:
tail -f /dev/null

and start it up again and you should be done.

Edited August 4Aug 4 by john_smith

On 8/5/2026 at 6:41 AM, john_smith said:

process is to add

tail -f /dev/null

to your "Extra Parameters" after toggling Advanced in edit container.

This completely broke my Container. After re-setting up the Container I found you put the above command into the

Post Arguments:

section.

Did the rest, and while the container now runs, Bichon's web page now loads a blank page. I'm hoping for an update, but this App seems to not have a lot of support

you need to remove the command after performing the upgrade

I have. Still no good

I as not able to reproduce this....
please post an issue on the github.

Thanks

Thanks. For now I'm going the delete the container and come back to this after a while.

Hi,

I installed Bichon in my Unraid environment with the default config brought by the container.
However, I'm not able to login (WebUI) with the default admin credentials (admin, admin@bichon).
It constantly throws an error "Something went wrong. Request failed with status code 403."

A reinstall dind't fix the problem.

Further, the WebUI only works in Firefox and using http but not in chromium based browsers (at least for me).

Does anybody has an idea what might be wrong and has a possible solution?

Many thanks in advance!

Edited Monday at 09:32 PM1 day by Schneemann
Clarified my login method.