Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usermod: group '101' does not exist on Docker image #6684

Closed
danfercf1 opened this issue Feb 23, 2024 · 2 comments
Closed

usermod: group '101' does not exist on Docker image #6684

danfercf1 opened this issue Feb 23, 2024 · 2 comments
Labels
kind/triage Unclassified issues

Comments

@danfercf1
Copy link

Problem Description

When I run the docker image using the command:

docker run --rm -it -v ~/.mitmproxy:/home/mitmproxy/.mitmproxy -p 192.168.1.103:8080:8080 mitmproxy/mitmproxy:9.0.0 mitmweb --mode wireguard --showhost

I receive the message "usermod: group '101' does not exist" and the container can't run, I've tried with the latest docker hub image and the problem is the same, I'm using Nobara that is a Fedora distribution based.

Steps to reproduce the behavior:

  1. Run the image with the command:
    docker run --rm -it -v ~/.mitmproxy:/home/mitmproxy/.mitmproxy -p 192.168.1.103:8080:8080 mitmproxy/mitmproxy:9.0.0 mitmweb --mode wireguard --showhost

System Information

mitmproxy 9.0.0
mitmproxy latest

@danfercf1 danfercf1 added the kind/triage Unclassified issues label Feb 23, 2024
@mhils
Copy link
Member

mhils commented Feb 26, 2024

The problem here is probably somewhere around -v ~/.mitmproxy:/home/mitmproxy/.mitmproxy and what we're doing here:

usermod -o \
-u $(stat -c "%u" "$f") \
-g $(stat -c "%g" "$f") \
mitmproxy

@danfercf1
Copy link
Author

I really don't know what was happened because I've tried again with this configuration
docker run --rm -it -v ~/.mitmproxy:/home/mitmproxy/.mitmproxy -p 192.168.1.103:8080:8080 -p 8081:8081 -p 51820:51820/udp mitmproxy/mitmproxy:latest mitmweb --mode wireguard --showhost --web-host 0.0.0.0 --set tls_version_client_min=SSL3 and it's working well now, I think the problem is fixed. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/triage Unclassified issues
Projects
None yet
Development

No branches or pull requests

2 participants