#4000 - [GH-ISSUE #5100] frpc | addgroup: gid '0' in use - github-starred/frp

gitea-mirror commented

2026-05-05 14:32:37 -06:00

Owner

Originally created by @aliuq on GitHub (Dec 21, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5100

Bug Description

snowdreamtech/frpc:0.65.0 startup error frpc | addgroup: gid '0' in use

frpc Version

0.65.0

frps Version

0.65.0

System Architecture

linux/amd64

Configurations

Synology

name: frpc

services:
  frpc:
    image: snowdreamtech/frpc:0.65.0
    restart: always
    container_name: frpc
    ports:
      - 18080:8080
    env_file:
      - .env
    volumes:
      - ./config:/etc/frp/
      - /etc/localtime:/etc/localtime:ro
    command: ["-c", "/etc/frp/frpc.toml"]
    environment:
      - TZ=Asia/Shanghai

Logs

No response

Steps to reproduce

0.64.0 has no problems.

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @aliuq on GitHub (Dec 21, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5100 ### Bug Description `snowdreamtech/frpc:0.65.0` startup error `frpc | addgroup: gid '0' in use` ### frpc Version 0.65.0 ### frps Version 0.65.0 ### System Architecture linux/amd64 ### Configurations Synology ```yaml name: frpc services: frpc: image: snowdreamtech/frpc:0.65.0 restart: always container_name: frpc ports: - 18080:8080 env_file: - .env volumes: - ./config:/etc/frp/ - /etc/localtime:/etc/localtime:ro command: ["-c", "/etc/frp/frpc.toml"] environment: - TZ=Asia/Shanghai ``` ### Logs _No response_ ### Steps to reproduce 0.64.0 has no problems. ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:32:37 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:32:40 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 22, 2025):

It’s caused by a third-party Docker image (snowdreamtech/frpc:0.65.0), not frp itself: its entrypoint tries to create a group with PGID=0 (GID 0 is already in use), typically because your env_file injects USER/PUID/PGID (e.g., USER becomes non-root while PGID stays 0).

@fatedier commented on GitHub (Dec 22, 2025): It’s caused by a third-party Docker image (snowdreamtech/frpc:0.65.0), not frp itself: its entrypoint tries to create a group with PGID=0 (GID 0 is already in use), typically because your env_file injects USER/PUID/PGID (e.g., USER becomes non-root while PGID stays 0).

gitea-mirror commented

2026-05-05 14:32:41 -06:00

Author

Owner

@aliuq commented on GitHub (Dec 22, 2025):

It’s caused by a third-party Docker image (snowdreamtech/frpc:0.65.0), not frp itself: its entrypoint tries to create a group with PGID=0 (GID 0 is already in use), typically because your env_file injects USER/PUID/PGID (e.g., USER becomes non-root while PGID stays 0).这是由第三方 Docker 镜像 (snowdreamtech/frpc:0.65.0) 引起的，而不是 frp 本身：它的入口点尝试创建一个 PGID=0 的组（GID 0 已被使用），通常是因为您的 env_file 注入了 USER/PUID/PGID（例如，USER 变为非 root 用户，而 PGID 保持为 0）。

Indeed, there is an environment traversal for USER in env_file; I'll try it later.

@aliuq commented on GitHub (Dec 22, 2025): > It’s caused by a third-party Docker image (snowdreamtech/frpc:0.65.0), not frp itself: its entrypoint tries to create a group with PGID=0 (GID 0 is already in use), typically because your env_file injects USER/PUID/PGID (e.g., USER becomes non-root while PGID stays 0).这是由第三方 Docker 镜像 (snowdreamtech/frpc:0.65.0) 引起的，而不是 frp 本身：它的入口点尝试创建一个 PGID=0 的组（GID 0 已被使用），通常是因为您的 env_file 注入了 USER/PUID/PGID（例如，USER 变为非 root 用户，而 PGID 保持为 0）。 Indeed, there is an environment traversal for USER in env_file; I'll try it later.

gitea-mirror commented

2026-05-05 14:32:41 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 6, 2026):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 6, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:50:32 -06:00

[PR #4000] [MERGED] proxy supports configuring annotations, which will be displayed in the frps dashboard #4882

gitea-mirror referenced this issue

2026-05-05 14:50:54 -06:00

[PR #4056] [MERGED] bump version #4902