alireza0 / s-ui

An advanced Web Panel • Built for SagerNet/Sing-Box
https://t.me/XrayUI
GNU General Public License v3.0
2.15k stars 307 forks source link

Start s-ui v0.0.3 error with docker compose #124

Closed leic4u closed 1 month ago

leic4u commented 1 month ago

Describe the bug I install s-ui with docker compose, my docker-compose.yml like this:

---
version: "3"

services:
  s-ui:
    image: alireza7/s-ui
    container_name: s-ui
    hostname: "S-UI docker"
    volumes:
      - "singbox:/app/bin"
      - "$PWD/db:/app/db"
      - "/root/nginx-ui/nginx/ssl/:/app/cert"
    environment:
      SINGBOX_API: "sing-box:1080"
      SUI_DB_FOLDER: "db"
    tty: true
    restart: unless-stopped
    ports:
      - "127.0.0.1:32095:2095"
      - "127.0.0.1:32096:2096"
    networks:
      - s-ui
    entrypoint: "./sui"

  sing-box:
    image: alireza7/s-ui-singbox
    container_name: sing-box
    volumes:
      - "singbox:/app/"
      - "/root/nginx-ui/nginx/ssl/:/cert"
    networks:
      - s-ui
    ports:
      - "4443:443"
      - "1443:1443"
      - "2443:2443"
      - "3443:3443"
    restart: unless-stopped
    depends_on:
      - s-ui

networks:
  s-ui:
    driver: bridge

volumes:
  singbox:

Which is forked from https://raw.githubusercontent.com/alireza0/s-ui/main/docker-compose.yml .

And when I run the docker compose up -d, the containers were exited immediately.

I check the docker logs s-ui and docker logs sing-box, there are only exec format error.

image

How could I do now to install s-ui v0.0.3 correctly?

alireza0 commented 1 month ago

As per your hostname, it seems you are using arm based server. Please make sure that the right package you are trying to use.

leic4u commented 1 month ago

As per your hostname, it seems you are using arm based server. Please make sure that the right package you are trying to use.

I check the images with docker inspect alireza7/s-ui:latest and docker inspect alireza7/s-ui-singbox:latest

images images

alireza0 commented 1 month ago

@leic4u Thank you dor your report. I have found the problem in my tests. Packages are now fixed and rebuilded. Pull the packages again and test it

leic4u commented 1 month ago

@leic4u Thank you dor your report. I have found the problem in my tests. Packages are now fixed and rebuilded. Pull the packages again and test it

I pulled the new images and it runs well.

but I can't access it because of HTTP ERROR 404.

both myip:32095 ( I changed the binded ports to 0.0.0.0:32095 ) and sui.mydomain.com ( the Nginx reverse proxy )

How could I access the sui panel? 😂

alireza0 commented 1 month ago

Did you use default path \app\ ?

leic4u commented 1 month ago

Did you use default path \app\ ?

Yes bro, I could access sui panel by sui.mydomain.com/app/ now.

It's my fault. I forgot to check it in readme.

Thanks again.