Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New issue since refreshing container #93

Open
VinneyUK opened this issue Jun 11, 2024 · 9 comments
Open

New issue since refreshing container #93

VinneyUK opened this issue Jun 11, 2024 · 9 comments

Comments

@VinneyUK
Copy link

Can someone help me understand why I am all of a sudden getting this error please?

s6-rc: info: service svc-openbox: starting s6-rc: info: service svc-novnc: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service svc-tigervnc successfully started s6-rc: info: service svc-openbox successfully started s6-rc: info: service svc-soulseek successfully started s6-rc: info: service svc-novnc successfully started s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-setup: starting Xvnc TigerVNC 1.13.1 - built 2024-04-01 08:26 Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101011 Tue Jun 11 19:26:01 2024 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started Warning: could not find self.pem Using local websockify at /usr/share/novnc/utils/websockify/run Starting webserver and WebSockets proxy on port 6080

@realies
Copy link
Owner

realies commented Jun 11, 2024

@VinneyUK, how do you start the container?

@VinneyUK
Copy link
Author

its within a stack in portainer.

@realies
Copy link
Owner

realies commented Jun 11, 2024

To be able to help, I need to reproduce your issue. How does Portainer start the container?

@VinneyUK
Copy link
Author

VinneyUK commented Jun 11, 2024

version: "3"
networks:
 mystack-vpn_default:
   ipam:
    driver: default 
    config:
     - subnet: 172.28.0.0/16
  
services:
  vpn:
    image: qmcgaw/gluetun
    container_name: vpn
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    networks: 
     mystack-vpn_default:
      ipv4_address: 172.28.0.2
    ports:
      - 8000:8000/tcp # Gluetun
      - 9000:9000 # theLounge
      - 113:9001 # theLounge
      - 9696:9696/tcp # prowlarr

      - 8282:8282/tcp # SABnzbd
      - 13000:3000 # filezilla
      - 55896:55896 #soulseek
      - 55897:55897 #soulseek
      - 2416:2416   #soulseek
      - 6080:6080   #soulseek 
      - 8181:8181    #qBitorrent 
      - 6881:6881     #qBitorrent
      - 8888:8888/tcp # HTTP proxy
      - 8388:8388/tcp # Shadowsocks
      - 8388:8388/udp # Shadowsocks
    volumes:
      - /home/dietpi/gluetun:/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - VPN_ENDPOINT_IP=
      - VPN_ENDPOINT_PORT=51820
      - WIREGUARD_PUBLIC_KEY=
      - WIREGUARD_PRIVATE_KEY=
      - WIREGUARD_ADDRESSES=10.2.0.2/32
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
      - VPN_PORTFORWARDING=ON
      - VPN_PORT_FORWARDING_STATUS_FILE=/tmp/gluetun/forwarded_port
      - FIREWALL_OUTBOUND_SUBNETS=172.28.0.0/16,192.168.50.0/24
    restart: unless-stopped

  prowlarr:
    image: lscr.io/linuxserver/prowlarr:latest
    container_name: prowlarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /home/dietpi/prowlarr:/config
  # ports:
  #   - 9696:9696
    restart: unless-stopped
    network_mode: service:vpn
    depends_on:
      - vpn

  sabnzbd:
    image: lscr.io/linuxserver/sabnzbd:latest
    container_name: sabnzbd
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /home/dietpi/sabnzbd:/config
      - /mnt/shared2/downloads/:/downloads #optional
      - /mnt/shared2/downloads/tmp/incomplete:/incomplete-downloads #optional
      - /mnt/shared2/downloads/tmp/watch:/watch #optional
  # ports:
  #   - 8282:8282
    restart: unless-stopped
    network_mode: service:vpn
    depends_on:
      - vpn
      
  thelounge:
    image: thelounge/thelounge:latest
    container_name: thelounge
    # ports:
    # - 113:9001
    # - 9000:9000
    volumes:
       - /home/dietpi/thelounge:/var/opt/thelounge
    restart: unless-stopped
    network_mode: service:vpn
    depends_on:
      - vpn

  soulseek:
    image: realies/soulseek
    container_name: soulseek
    security_opt:
      - seccomp:unconfined
    volumes:
      - '/home/dietpi/soulseek/appdata:/data/.SoulseekQt'
      - '/mnt/shared2/Downloads/unsorted:/data/Downloads:rw'
      - '/home/dietpi/soulseek/logs:/data/Soulseek Chat Logs'
      - '/mnt/shared/Lossy Music:/data/Lossy'
      - '/mnt/shared/Packs:/data/Packs'
      - '/mnt/shared/Rare Acapellas:/data/Rare Acapellas'
      - '/mnt/shared2/Lossless Music:/data/Lossless'
      - '/mnt/shared/Exclusive:/data/Exclusive'
    environment:
      - UMASK=022
      - PGID=0
      - PUID=0
    network_mode: service:vpn
    depends_on:
      - vpn

  qbittorrent:
    image: linuxserver/qbittorrent:latest
    container_name: qbittorrent2
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - UMASK=022
      - WEBUI_PORT=8181
      - DOCKER_MODS=arafatamim/linuxserver-io-mod-vuetorrent
    volumes:
      - /home/dietpi/qbittorrent:/config
      - /mnt/shared2/downloads/unsorted:/downloads #optional
      - /mnt/shared2/downloads/tmp/incomplete:/incomplete-downloads #optional
      - /mnt/shared2/downloads/tmp/watch:/watch #optional
  # ports:
  #   - 8181:8181
  #   - 6881:6881
  #   - 6881:6881/udp
    labels:
      - autoheal=true
    healthcheck:
      test: curl google.com || exit 1
      interval: 30s
      timeout: 10s
      retries: 3
    network_mode: service:vpn
    depends_on:
      - vpn

@VinneyUK
Copy link
Author

@realies does that help?

@realies
Copy link
Owner

realies commented Jun 11, 2024

I've tried this in a simpler compose stack, while trying to retain most of the specifics you have in yours:

version: '2'
services:
  soulseek:
    security_opt:
      - seccomp:unconfined
    platform: linux/amd64
    image: realies/soulseek
    environment:
      - UMASK=022
      - PGID=0
      - PUID=0
    ports:
      - 6080:6080
    volumes:
      - appdata:/data/.SoulseekQt
      - downloads:/data/Soulseek Downloads
      - shared:/data/Soulseek Shared Folder
      - logs:/data/Soulseek Chat Logs
volumes:
  appdata:
  downloads:
  shared:
  logs:

And it works fine:

$ docker compose up                                                                                                                                                           
WARN[0000] /home/realies/projects/soulseek-docker/docker-compose.yml: `version` is obsolete                                                                                                                           
[+] Running 2/0                                                                                                                                                                                                       
 ✔ Network soulseek-docker_default       Created                                                                                                                                                                 0.1s 
 ✔ Container soulseek-docker-soulseek-1  Created                                                                                                                                                                 0.0s 
Attaching to soulseek-1                                                                                                                                                                                               
soulseek-1  | s6-rc: info: service svc-tigervnc: starting                                                                                                                                                             
soulseek-1  | s6-rc: info: service svc-soulseek: starting                                                                                                                                                             
soulseek-1  | s6-rc: info: service svc-openbox: starting                                                                                                                                                              
soulseek-1  | s6-rc: info: service svc-novnc: starting                                                                                                                                                                
soulseek-1  | s6-rc: info: service s6rc-oneshot-runner: starting                                                                                                                                                      
soulseek-1  | s6-rc: info: service svc-tigervnc successfully started                                                                                                                                                  
soulseek-1  | s6-rc: info: service svc-soulseek successfully started                                                                                                                                                  
soulseek-1  | s6-rc: info: service svc-openbox successfully started                                                                                                                                                   
soulseek-1  | s6-rc: info: service svc-novnc successfully started
soulseek-1  | s6-rc: info: service s6rc-oneshot-runner successfully started
soulseek-1  | s6-rc: info: service fix-attrs: starting
soulseek-1  | s6-rc: info: service init-setup: starting
soulseek-1  | s6-rc: info: service fix-attrs successfully started
soulseek-1  | s6-rc: info: service legacy-cont-init: starting
soulseek-1  | 
soulseek-1  | Xvnc TigerVNC 1.13.1 - built 2024-04-01 08:26
soulseek-1  | Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
soulseek-1  | See https://www.tigervnc.org for information on TigerVNC.
soulseek-1  | Underlying X server release 12101011
soulseek-1  | 
soulseek-1  | 
soulseek-1  | Tue Jun 11 19:48:19 2024
soulseek-1  |  vncext:      VNC extension running!
soulseek-1  |  vncext:      Listening for VNC connections on all interface(s), port 5900
soulseek-1  |  vncext:      created VNC server for screen 0
soulseek-1  | Warning: could not find self.pem
soulseek-1  | Using local websockify at /usr/share/novnc/utils/websockify/run
soulseek-1  | s6-rc: info: service legacy-cont-init successfully started
soulseek-1  | Starting webserver and WebSockets proxy on port 6080
soulseek-1  | s6-rc: info: service init-setup successfully started
soulseek-1  | s6-rc: info: service legacy-services: starting
soulseek-1  | s6-rc: info: service legacy-services successfully started
soulseek-1  | The XKEYBOARD keymap compiler (xkbcomp) reports:
soulseek-1  | > Warning:          Could not resolve keysym XF86CameraAccessEnable
soulseek-1  | > Warning:          Could not resolve keysym XF86CameraAccessDisable
soulseek-1  | > Warning:          Could not resolve keysym XF86CameraAccessToggle
soulseek-1  | > Warning:          Could not resolve keysym XF86NextElement
soulseek-1  | > Warning:          Could not resolve keysym XF86PreviousElement
soulseek-1  | > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
soulseek-1  | > Warning:          Could not resolve keysym XF86MarkWaypoint
soulseek-1  | > Warning:          Could not resolve keysym XF86Sos
soulseek-1  | > Warning:          Could not resolve keysym XF86NavChart
soulseek-1  | > Warning:          Could not resolve keysym XF86FishingChart
soulseek-1  | > Warning:          Could not resolve keysym XF86SingleRangeRadar
soulseek-1  | > Warning:          Could not resolve keysym XF86DualRangeRadar
soulseek-1  | > Warning:          Could not resolve keysym XF86RadarOverlay
soulseek-1  | > Warning:          Could not resolve keysym XF86TraditionalSonar
soulseek-1  | > Warning:          Could not resolve keysym XF86ClearvuSonar
soulseek-1  | > Warning:          Could not resolve keysym XF86SidevuSonar
soulseek-1  | > Warning:          Could not resolve keysym XF86NavInfo
soulseek-1  | Errors from xkbcomp are not fatal to the X server
soulseek-1  | [mi] mieq: warning: overriding existing handler (nil) with 0x597b5f47f580 for event 2
soulseek-1  | [mi] mieq: warning: overriding existing handler (nil) with 0x597b5f47f580 for event 3
soulseek-1  | WebSocket server settings:
soulseek-1  |   - Listen on :6080
soulseek-1  |   - Web server. Web root: /usr/share/novnc
soulseek-1  |   - No SSL/TLS support (no cert file)
soulseek-1  |   - proxying from :6080 to localhost:5900
soulseek-1  | 
soulseek-1  | 
soulseek-1  | Navigate to this URL:
soulseek-1  | 
soulseek-1  |     http://44062e49d10b:6080/vnc.html?host=44062e49d10b&port=6080
soulseek-1  | 
soulseek-1  | Press Ctrl-C to exit
soulseek-1  | 
soulseek-1  | 

Where do you see an error? Your first comment contains a warning.

@VinneyUK
Copy link
Author

@realies let me investigate further when I have time, and will get back to you. Thank you.,

@VinneyUK
Copy link
Author

@realies can I rollback to a earlier version?

@realies
Copy link
Owner

realies commented Jun 11, 2024

You can check out this repository at an earlier commit and build an image from it. Probably better to debug what's going wrong if it does not work. Are you sure it does not work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants