[GH-ISSUE #1311] bitwarden_rs bug whit docker-compose and docker run #908

New issue

Closed

opened 2026-03-03 02:04:35 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:04:35 +03:00

Owner

Originally created by @Ran-Xing on GitHub (Jan 15, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1311

Sorry, I can't understand English
left : docker-compose up -d right: docker run

Originally created by @Ran-Xing on GitHub (Jan 15, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1311 Sorry, I can't understand English left : docker-compose up -d right: docker run ![image](https://user-images.githubusercontent.com/73819467/104731271-6d832200-5776-11eb-8ac5-a2ab4bd63bc0.png) ![image](https://user-images.githubusercontent.com/73819467/104731535-cb176e80-5776-11eb-9ecd-2857c79b8ad3.png)

kerem closed this issue

2026-03-03 02:04:35 +03:00

kerem commented

2026-03-03 02:04:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Jan 17, 2021):

So, what is the bug then? It seems started just fine except that it couldn't read the ssl cert correctly.
Also, you have duplicate ports there, if you do not add /tcp or /udp it defaults to both, so adding /udp is useless.

Other than that it looks ok, it starts, shows on which ports it is running.

@BlackDex commented on GitHub (Jan 17, 2021): So, what is the bug then? It seems started just fine except that it couldn't read the ssl cert correctly. Also, you have duplicate ports there, if you do not add /tcp or /udp it defaults to both, so adding /udp is useless. Other than that it looks ok, it starts, shows on which ports it is running.

kerem commented

2026-03-03 02:04:36 +03:00

Author

Owner

@Ran-Xing commented on GitHub (Jan 17, 2021):

@BlackDex oh ,TKS,I thought it was just the UDP port by default. Let me see. I backed up the data

@Ran-Xing commented on GitHub (Jan 17, 2021): @BlackDex oh ,TKS,I thought it was just the UDP port by default. Let me see. I backed up the data

kerem commented

2026-03-03 02:04:36 +03:00

Author

Owner

@Ran-Xing commented on GitHub (Jan 17, 2021):

Sorry , Because I use the Intranet environment, so I signed a certificate, under normal circumstances
The docker run command can be parsed normally, but docker compose up - d just can't. I just applied for a formal SSL certificate, but it doesn't seem to work either

Docker management software Portainer 1.24

And I use my own SSL certificate issued by other containers can work normally, but at present only this one is docker-compose up-d can not work normally, docker run can work normally

@Ran-Xing commented on GitHub (Jan 17, 2021): Sorry , Because I use the Intranet environment, so I signed a certificate, under normal circumstances The docker run command can be parsed normally, but docker compose up - d just can't. I just applied for a formal SSL certificate, but it doesn't seem to work either ![image](https://user-images.githubusercontent.com/73819467/104846561-1c119900-5916-11eb-8d08-24eaf176f2d4.png) Docker management software Portainer 1.24 ![image](https://user-images.githubusercontent.com/73819467/104846589-419ea280-5916-11eb-9380-194cdd0bcbf0.png) And I use my own SSL certificate issued by other containers can work normally, but at present only this one is docker-compose up-d can not work normally, docker run can work normally

kerem referenced this issue

2026-03-03 08:53:14 +03:00

[PR #919] [MERGED] Fixed issue #908 #2825