Error after podman container startup #864

Closed
opened 2026-02-04 23:08:29 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @filovitch on GitHub (Nov 19, 2020).

Hi everyone,
When I start a birtwarden_rs rootless container under podman, I have this error at startup.

[filovitch@podman-host podman]$ podman run -d --name bitwarden -v /home/filovitch/podman/bitwarden/data/:/data/:Z -e ROCKET_PORT=8080 -e LOG_FILE=/data/bitwarden.log -p 8081:8080 docker.io/bitwardenrs/server:latest
ERRO[0000] exit status 1                                
ERRO[0000] Unit 5ffc321833dedb69b7b9c32e053e6136ae9c9d47073def6cc65cf1f7c895bd06.service not found. 
5ffc321833dedb69b7b9c32e053e6136ae9c9d47073def6cc65cf1f7c895bd06
[filovitch@podman-host podman]$ cat bitwarden/data/bitwarden.log 
[2020-11-19 07:33:06.369][start][INFO] Rocket has launched from http://0.0.0.0:8080  
[filovitch@podman-host podman]$ podman logs bitwarden
/--------------------------------------------------------------------\
|                       Starting Bitwarden_RS                        |
|                           Version 1.17.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://bitwardenrs.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/bitwarden_rs/issues/new           |
\--------------------------------------------------------------------/

[2020-11-19 07:33:06.369][start][INFO] Rocket has launched from http://0.0.0.0:8080
[filovitch@podman-host podman]$ 

The container is running but I suppose this error is not normal.

My config is:

[filovitch@podman-host podman]$ cat /etc/redhat-release 
CentOS Linux release 8.2.2004 (Core) 
[filovitch@podman-host podman]$ podman version
Version:            1.6.4
RemoteAPI Version:  1
Go Version:         go1.13.4
OS/Arch:            linux/amd64
Originally created by @filovitch on GitHub (Nov 19, 2020). Hi everyone, When I start a birtwarden_rs rootless container under podman, I have this error at startup. ``` [filovitch@podman-host podman]$ podman run -d --name bitwarden -v /home/filovitch/podman/bitwarden/data/:/data/:Z -e ROCKET_PORT=8080 -e LOG_FILE=/data/bitwarden.log -p 8081:8080 docker.io/bitwardenrs/server:latest ERRO[0000] exit status 1 ERRO[0000] Unit 5ffc321833dedb69b7b9c32e053e6136ae9c9d47073def6cc65cf1f7c895bd06.service not found. 5ffc321833dedb69b7b9c32e053e6136ae9c9d47073def6cc65cf1f7c895bd06 [filovitch@podman-host podman]$ cat bitwarden/data/bitwarden.log [2020-11-19 07:33:06.369][start][INFO] Rocket has launched from http://0.0.0.0:8080 [filovitch@podman-host podman]$ podman logs bitwarden /--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.17.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://bitwardenrs.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/bitwarden_rs/issues/new | \--------------------------------------------------------------------/ [2020-11-19 07:33:06.369][start][INFO] Rocket has launched from http://0.0.0.0:8080 [filovitch@podman-host podman]$ ``` The container is running but I suppose this error is not normal. My config is: ``` [filovitch@podman-host podman]$ cat /etc/redhat-release CentOS Linux release 8.2.2004 (Core) [filovitch@podman-host podman]$ podman version Version: 1.6.4 RemoteAPI Version: 1 Go Version: go1.13.4 OS/Arch: linux/amd64 ```
OVERLORD added the Third partybetter for forum labels 2026-02-04 23:08:29 +03:00
Author
Owner

@BlackDex commented on GitHub (Nov 20, 2020):

Hello @filovitch, that error has nothing to do with bitwardenrs it self i think. More a podman issue or something else.
So no idea what could be wrong here

@BlackDex commented on GitHub (Nov 20, 2020): Hello @filovitch, that error has nothing to do with bitwardenrs it self i think. More a podman issue or something else. So no idea what could be wrong here
Author
Owner

@davidjameshowell commented on GitHub (Nov 28, 2020):

For what it is worth, I have gotten this error each and every time my rootless Podman instance comes up. I've ignored it and I believe is a benign Podman issue.

@davidjameshowell commented on GitHub (Nov 28, 2020): For what it is worth, I have gotten this error each and every time my rootless Podman instance comes up. I've ignored it and I believe is a benign Podman issue.
Author
Owner

@BlackDex commented on GitHub (Dec 3, 2020):

Closing this ticket as this is not an issue with bitwarden_rs.
Feel free to continue this discussion on the forum: https://bitwardenrs.discourse.group/

@BlackDex commented on GitHub (Dec 3, 2020): Closing this ticket as this is not an issue with bitwarden_rs. Feel free to continue this discussion on the forum: https://bitwardenrs.discourse.group/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#864