Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

UserUID collision: node-red(1000) by default

Open
#146 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose, shell

Research direction

Start by examining the Docker image configuration and the docker-compose setup used to reproduce the UID collision. Compare the current container user setup with the referenced commit d5ff167e5ad1351af31bc8bf9dd3304d59ee5ff0. Done means allowing the container user UID to be set manually without colliding with the host user's UID.

Written by the indexing model from the issue text.

Description

What are the steps to reproduce?

Run docker-compose\docker with mounting local directory to container.

What happens?

User from container will be mapped to me. UID collision with first user in linux occured :-(

What do you expect to happen?

I can manually set user uid in container

It's may be fixed by https://github.com/pkjq/node-red-docker/commit/d5ff167e5ad1351af31bc8bf9dd3304d59ee5ff0

Dominant language
Shell
Stars
540
Forks
434
Avg merge
24m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from node-red/node-red-docker

All issues in node-red/node-red-docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.