crazy-max / docker-rtorrent-rutorrent

rTorrent and ruTorrent Docker image
MIT License
457 stars 103 forks source link

Update to 4.3.0 not possible - rutorrent breaks #345

Closed dstyp closed 1 month ago

dstyp commented 1 month ago

Support guidelines

I've found a bug and checked that ...

Description

Wanted to update to 4.3.0 but it breaks. Had to revert and am now using image: crazymax/rtorrent-rutorrent:4.2.9-0.9.8_2-0.13.8_2 in compose.yml.

Expected behaviour

Rutorrent to work

Actual behaviour

Many error messages, I have a screen shot

[15.05.2024 21:59:06] WebUl started. [15.05.2024 21:59:07]JS error: [http://192.168.1.100:8080/: 3015] Uncaught ReferenceError: injectCustomElementCSS is not defined [15.05.2024 21:59:071 Bad response from server: (404 [error,listl) < html> < title >404 Not Found ‹center>

404 Not Found


nginx
page --> <!-- a padding to disable MSIE and Chrome friendly error page -→>

Screenshot 2024-05-15 at 21 59 30

Steps to reproduce

1 set compose.yml to latest 2 pull & start 3 doesnt work

Docker info

Client: Docker Engine - Community
 Version:    26.1.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.26.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 8
  Running: 6
  Paused: 0
  Stopped: 2
 Images: 99
 Server Version: 26.1.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.0-20-amd64
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 31.2GiB
 Name: dsrvxxii
 ID: 30913477-cafc-44ba-86d0-1eafd7a92d18
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Docker Compose config

No response

Logs

will have to get back on this

Additional info

No response

SnorreSelmer commented 1 month ago

Yep, having the exact same issue here. latest fails to work with a 404, 4.2.9-0.9.8_2-0.13.8_2 works fine

stickz commented 1 month ago

Hello @dstyp @SnorreSelmer There are two steps required to upgrade to latest.

1) Clear your web browser cache. 2) Set RU_REMOVE_CORE_PLUGINS environment variable to false. The 404 error is caused by removing the httprpc plugin from the previous version of the docker container. This is now required for ruTorrent v4.3.0, as we dropped support for rpc.

Please do not hesitate to ask, if you have any further questions about this version upgrade. There are very significant and impactful changes to the docker container. It highly recommended to invest 15 minutes of your time into upgrading.

crazy-max commented 1 month ago

Set RU_REMOVE_CORE_PLUGINS environment variable to false.

@stickz Let me know if we should add this to the changelog or feel to open a PR 👍

stickz commented 1 month ago

@dstyp @SnorreSelmer Please pull the latest ruTorrent v4.3.1 docker image @crazy-max just tagged. This will automatically resolve your problem. You'll receive a warning instead and ruTorrent v4.3.1 will load successfully.

dstyp commented 1 month ago

@stickz @crazy-max great stuff just in time for the weekend. Thank you for the efforts! 🙏⭐️