crazy-max / docker-rtorrent-rutorrent

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

After each release/update the torrent list is removed ARM64 #298

Closed djayor closed 2 months ago

djayor commented 6 months ago

Support guidelines

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

Description

My containers are updated whenever a new version is released via Watchtower. I currently have 3 machines, 2 with ARM64 and another with AMD64. Whenever the container is updated on ARM64 machines, the torrent list is removed and the /data/rtorrent/.rtorrent.rc file is reset to default.

Expected behaviour

It is expected that after the update the torrent list and the .rtorrent.rc file will remain intact. On AMD64 machines the list remains and the file are intact after the update.

Actual behaviour

But on machines with the ARM64 tag, the torrent list is removed, and .rtorrent.rc is reset to default.

Steps to reproduce

This happens without my intervention only after updating. Even if you don't use the watchtower to perform the automatic update and manually edit the image of crazymax/rtorrent-rutorrent:current to crazymax/rtorrent-rutorrent:latest on the portainer.

Docker info

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

Server:
 Containers: 12
  Running: 11
  Paused: 0
  Stopped: 1
 Images: 11
 Server Version: 24.0.7
 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 logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dd1e886e55dd695541fdcd67420c2888645a495
 runc version: v1.1.10-0-g18a0cb0
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.21-v8+
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 7.457GiB
 Name: Name1
 ID: c784d74b-9505-44ef-8ccb-8303a275111d
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No memory limit support
WARNING: No swap limit support

Docker Compose config

No response

Logs

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-fix-logs.sh: executing... 
[cont-init.d] 00-fix-logs.sh: exited 0.
[cont-init.d] 01-fix-uidgid.sh: executing... 
[cont-init.d] 01-fix-uidgid.sh: exited 0.
[cont-init.d] 02-fix-perms.sh: executing... 
Fixing perms...
[cont-init.d] 02-fix-perms.sh: exited 0.
[cont-init.d] 03-config.sh: executing... 
Setting timezone to America/New_York...
Setting PHP-FPM configuration...
Setting PHP INI configuration...
Setting OpCache configuration...
Setting Nginx configuration...
Setting Nginx XMLRPC over SCGI configuration...
Setting Nginx ruTorrent configuration...
Setting Nginx WebDAV configuration...
Update healthcheck script...
Initializing files and folders...
rpc.htpasswd is empty, removing authentication...
rutorrent.htpasswd is empty, removing authentication...
webdav.htpasswd is empty, removing authentication...
Checking rTorrent local configuration...
Checking rTorrent configuration...
  Creating default configuration...
Bootstrapping ruTorrent configuration...
Symlinking ruTorrent access.ini file...
Symlinking ruTorrent plugins.ini file...
Removing core plugin erasedata...
Removing core plugin httprpc...
Setting custom config for create plugin...
Checking ruTorrent custom plugins...
Checking ruTorrent plugins configuration...
Checking ruTorrent custom themes...
Setting GeoIP2 databases for geoip2 plugin...
Fixing perms...
[cont-init.d] 03-config.sh: exited 0.
[cont-init.d] 04-create-services.sh: executing... 
[cont-init.d] 04-create-services.sh: exited 0.
[cont-init.d] ~-socklog: executing... 
[cont-init.d] ~-socklog: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2023/12/23 18:49:53 [notice] 517#517: using the "epoll" event method
2023/12/23 18:49:53 [notice] 517#517: nginx/1.24.0
2023/12/23 18:49:53 [notice] 517#517: OS: Linux 6.1.21-v8+
2023/12/23 18:49:53 [notice] 517#517: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/12/23 18:49:53 [notice] 517#517: start worker processes
2023/12/23 18:49:53 [notice] 517#517: start worker process 548
2023/12/23 18:49:53 [notice] 517#517: start worker process 549
2023/12/23 18:49:53 [notice] 517#517: start worker process 550
2023/12/23 18:49:53 [notice] 517#517: start worker process 551
[23-Dec-2023 18:49:53] NOTICE: fpm is running, pid 521
[23-Dec-2023 18:49:53] NOTICE: ready to handle connections

Additional info

If the information is incomplete, I can provide more data. Thanks

stickz commented 6 months ago

It looks like something is outdated on your end for the ARM64 machine. Removing core plugin erasedata... This was deprecated when the erasedata plugin on ruTorrent was improved.

This line here is where your tripping at for the .rtorrent.rc file being reset. https://github.com/crazy-max/docker-rtorrent-rutorrent/blob/1efb9e087f90f68ed132b3ffd419b29145a1838e/rootfs/etc/cont-init.d/03-config.sh#L196

djayor commented 6 months ago

I removed the container, and the image and did a clean install. Tonight the same happened, the container was updated and the torrent list was cleaned again.

Should I comment the line 196 to 199 ?

crazy-max commented 2 months ago

I'm not able to repro after bump to latest. Closing this one in the meantime but feel free to continue the discussion if it still occurs on your side.