github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-17 17:32:27 -05:00
Code Issues 489 Packages Projects Releases 83 Wiki Activity

Docker in container unreachable #35

New Issue
Closed
opened 2025-11-07 06:19:39 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-07 06:19:39 -06:00
Owner
Copy Link

Originally created by @lablans on GitHub (Jul 12, 2018).

This is about @mprasil's container: Newest version listens on localhost rather than 0.0.0.0. As a result, docker cannot expose the port and Bitwarden is unreachable.

Steps to reproduce:

# docker run -d --rm --name bitwarden --user 1002 -e ROCKET_PORT=8080 -v /srv/bitwarden/:/data/ -p 127.0.0.1:32080:8080 mprasil/bitwarden:latest
c6e390f52c899b0af595143d9692fd2644a0d7e18c8a4350fb834ebd38ac0618
# wget http://localhost:32080
--2018-07-12 13:34:16--  http://localhost:32080/
Resolving localhost (localhost)... 127.0.0.1, ::1
Connecting to localhost (localhost)|127.0.0.1|:32080... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

Previous image 110e31f98241 runs fine.

Originally created by @lablans on GitHub (Jul 12, 2018). This is about @mprasil's container: Newest version listens on localhost rather than 0.0.0.0. As a result, docker cannot expose the port and Bitwarden is unreachable. Steps to reproduce: ``` # docker run -d --rm --name bitwarden --user 1002 -e ROCKET_PORT=8080 -v /srv/bitwarden/:/data/ -p 127.0.0.1:32080:8080 mprasil/bitwarden:latest c6e390f52c899b0af595143d9692fd2644a0d7e18c8a4350fb834ebd38ac0618 # wget http://localhost:32080 --2018-07-12 13:34:16-- http://localhost:32080/ Resolving localhost (localhost)... 127.0.0.1, ::1 Connecting to localhost (localhost)|127.0.0.1|:32080... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. ``` Previous image `110e31f98241` runs fine.
GiteaMirror commented 2025-11-07 06:19:41 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Jul 12, 2018):

Hmm for some reason ROCKET_ENV is not applied correctly. Oddly enough you can run the container fine if you set the variable directly:

 -e ROCKET_ENV=staging

Edit: Actually it's because it's defined at wrong spot in the node image and not the resulting one. Going to fire up an PR for that.

@mprasil commented on GitHub (Jul 12, 2018): Hmm for some reason `ROCKET_ENV` is not applied correctly. Oddly enough you can run the container fine if you set the variable directly: ``` -e ROCKET_ENV=staging ``` Edit: Actually it's because it's defined at wrong spot in the node image and not the resulting one. Going to fire up an PR for that.
GiteaMirror commented 2025-11-07 06:19:41 -06:00
Author
Owner
Copy Link

@ptman commented on GitHub (Jul 12, 2018):

I was just also going to chime in about the inconsistency between README and the ports actually in use in the image.

@ptman commented on GitHub (Jul 12, 2018): I was just also going to chime in about the inconsistency between README and the ports actually in use in the image.
GiteaMirror commented 2025-11-07 06:19:41 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Jul 12, 2018):

I'm just testing the PR. Once verified in next ~10 minutes, I'll push and trigger the build on docker hub. In the meantime you can start the container with -e ROCKET_ENV=staging as a quick workaround.

@mprasil commented on GitHub (Jul 12, 2018): I'm just testing the PR. Once verified in next ~10 minutes, I'll push and trigger the build on docker hub. In the meantime you can start the container with `-e ROCKET_ENV=staging` as a quick workaround.
GiteaMirror commented 2025-11-07 06:19:41 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Jul 12, 2018):

The code has been merged and pushed, build is now triggered, you should be able to follow it here. Once done (this usually takes just slightly less than one hour) you should be good to use the latest image.

@mprasil commented on GitHub (Jul 12, 2018): The code has been merged and pushed, build is now triggered, you should be able to follow it [here](https://hub.docker.com/r/mprasil/bitwarden/builds/bmz7wvczwv36halqwkk4pel/). Once done (this usually takes just slightly less than one hour) you should be good to use the latest image.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#35
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?