mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #234] Docker container only for UI #3229
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#3229
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @schmittyd on GitHub (Dec 13, 2023).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/234
Is your feature request related to a problem? Please describe.
I want to include just the UI in my Docker compose as I already have a SWAG container which has NGINX, Certbot and php.
Describe the solution you'd like
A separate container just for the UI.
@0xJacky commented on GitHub (Dec 13, 2023):
Hi, in nginx-ui, we need to execute some commands directly in the same environment with Nginx like to restart or reload it. If using a separate container just for the UI, we cannot control, test config files or get the running status of nginx.
@schmittyd commented on GitHub (Dec 13, 2023):
Could you possibly add the GUI as a Docker mod to the NGINX and SWAG containers?
https://github.com/linuxserver/docker-mods
@leoperegrino commented on GitHub (Jan 3, 2024):
bump. this would be useful for those who already are running nginx images and prefer not to switch. I use
linuxserver/nginxwhich has few modifications such as configurations mountpoints (/config), users and groups.In case of a different image only for the UI, a form of communication of the UI and the separate nginx would be necessary. I think of shared volumes or network calls.
Shared volumes are ok if one only needs to read and write to configuration/log files, not execute commands. I don't know if nginx provides any type of RPCs or APIs for command execution, and even if it does that would pose a security risk.
Why having a shared mount between a nginx-ui UI container and a different nginx container is not enough? Maybe the only option is what @schmittyd sugested.
@Mqxx commented on GitHub (Feb 26, 2025):
It would definitely! For example I wan't to use my own Nginx because I need the RTMP module and I can not "build it into" this existing Nginx-UI container. The RTMP module requires Nginx to be build from scratch to include the community RTMP module. https://github.com/0xJacky/nginx-ui/issues/856
@jo-chemla commented on GitHub (Jul 1, 2025):
Thanks for the implementation of managing nginx in another docker container in #977!
@Mqxx commented on GitHub (Jul 3, 2025):
Are there any documentation on how to set this up? https://github.com/0xJacky/nginx-ui/discussions/1151
@0xJacky commented on GitHub (Jul 3, 2025):
Please check this documentation: https://nginxui.com/guide/config-nginx.html#container-control
@Mqxx commented on GitHub (Jul 3, 2025):
Thanks! I will try that 🙂
@Mqxx commented on GitHub (Jul 3, 2025):
If I understand correctly I just need to specify an
envvariable in the docker-compose.yml calledNGINX_UI_NGINX_CONTAINER_NAME=that points to the name of the container for the nginx instance.@0xJacky commented on GitHub (Jul 3, 2025):
Yes, you're right.
@Mqxx commented on GitHub (Jul 3, 2025):
So for example my docker-compose.yml would look like this?
@Mqxx commented on GitHub (Jul 7, 2025):
@0xJacky I tried the
docker-compose.ymlconfig that I posted, but now I have multiple problems. First of all it looks like nginx-ui creates a default user callednginxbut this user does not exist so the custom image crashes, second problem is that I can not restart the image using the ui (I suppose this is because the custom image runs in a separate container). Is there a way I can fix these problems?