[GH-ISSUE #418] [QUESTION] container won't start - "exec user process caused: operation not permitted" #282

New issue

Closed

opened 2026-02-25 20:35:19 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 20:35:19 +03:00

Owner

Originally created by @allenwalker3 on GitHub (Sep 6, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/418

I cloned the repo, running in the main branch. Tried 'docker-compose up -d' but get this error in the logs:

$ sudo docker-compose logs -f
Attaching to whoogle-search
whoogle-search    | standard_init_linux.go:228: exec user process caused: operation not permitted
whoogle-search    | standard_init_linux.go:228: exec user process caused: operation not permitted
whoogle-search    | standard_init_linux.go:228: exec user process caused: operation not permitted
whoogle-search    | standard_init_linux.go:228: exec user process caused: operation not permitted
whoogle-search    | standard_init_linux.go:228: exec user process caused: operation not permitted

In docker-compose.yml changed 'user' from '102' to '114' as my system has tor running outside the container, and debian-tor user id is 114.

If I run in the master branch, everything loads ok.

Originally created by @allenwalker3 on GitHub (Sep 6, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/418 I cloned the repo, running in the main branch. Tried 'docker-compose up -d' but get this error in the logs: ``` $ sudo docker-compose logs -f Attaching to whoogle-search whoogle-search | standard_init_linux.go:228: exec user process caused: operation not permitted whoogle-search | standard_init_linux.go:228: exec user process caused: operation not permitted whoogle-search | standard_init_linux.go:228: exec user process caused: operation not permitted whoogle-search | standard_init_linux.go:228: exec user process caused: operation not permitted whoogle-search | standard_init_linux.go:228: exec user process caused: operation not permitted ``` In docker-compose.yml changed 'user' from '102' to '114' as my system has tor running outside the container, and debian-tor user id is 114. If I run in the master branch, everything loads ok.

kerem

2026-02-25 20:35:19 +03:00

closed this issue
added the
question

needs more info
labels

kerem commented

2026-02-25 20:35:20 +03:00

Author

Owner

@benbusby commented on GitHub (Oct 12, 2021):

I haven't been able to reproduce this one yet. The user ID for debian-tor within the container spun up by docker-compose should always be 102 no matter what, though. Did you shell into the container to check the user ID before changing it?

@benbusby commented on GitHub (Oct 12, 2021): I haven't been able to reproduce this one yet. The user ID for debian-tor within the container spun up by docker-compose should always be 102 no matter what, though. Did you shell into the container to check the user ID before changing it?