Skip to content
Discussion options

You must be logged in to vote

If you don’t want to run the container as non-root, you can force it to run as root by editing your docker-compose.yml and adding the user directive:

services:
  wiredoor:
    image: wiredoor/wiredoor:latest
    user: root
    # ...

This way the container will behave the same as in previous releases.

However, we recommend the non-root setup for better security.

Thanks to your feedback I was able to reproduce the issue and I’ve added the proper upgrade steps to the release notes.

Replies: 6 comments 9 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@dmesad
Comment options

Comment options

You must be logged in to vote
1 reply
@dmesad
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
7 replies
@er2de2
Comment options

@er2de2
Comment options

@er2de2
Comment options

@dmesad
Comment options

Answer selected by dmesad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants