[bug] Is the latest docker image broken?

[faywong]

Description of the bug

I follow the instructions at https://www.filestash.app/docs/install-and-upgrade/#installation to deploy filestash.

The docker image succeed to startup, but the 8334 can't be accessed any more.

ERR_CONNECTION_REFUSED

Step by step instructions to reproduce the bug

Just as https://www.filestash.app/docs/install-and-upgrade/#installation

mkdir filestash && cd filestash
curl -O https://downloads.filestash.app/latest/docker-compose.yml
docker-compose up -d

Observed behavior

the filestash docker log:

2024/12/29 13:02:25 SYST INFO [http] starting ...

2024/12/29 13:02:26 SYST INFO [http] listening on :443

the filestash_wopi log:

wsd-00009-00030 2024-12-29 13:02:35.247131 +0000 [ prisoner_poll ] TRC  #16: setupPollFds getPollEvents: 0x1| net/Socket.hpp:964

wsd-00009-00030 2024-12-29 13:02:35.247134 +0000 [ prisoner_poll ] TRC  #17: setupPollFds getPollEvents: 0x1| net/Socket.hpp:964

wsd-00009-00030 2024-12-29 13:02:35.247138 +0000 [ prisoner_poll ] TRC  ppoll start, timeoutMicroS: 15968364 size 3| net/Socket.cpp:512

wsd-00009-00009 2024-12-29 13:02:35.247138 +0000 [ coolwsd ] TRC  Have 1 new children.| wsd/COOLWSD.cpp:3656

wsd-00009-00009 2024-12-29 13:02:35.247156 +0000 [ coolwsd ] INF  WSD initialization complete: setting log-level to [warning] as configured.| wsd/COOLWSD.cpp:3671

Ready to accept connections on port 9980.

wsd-00009-00009 2024-12-29 13:02:35.247863 +0000 [ coolwsd ] WRN  Waking up dead poll thread [main], started: false, finished: false| net/Socket.hpp:808

frk-00031-00031 2024-12-29 13:02:35.248236 +0000 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

frk-00031-00031 2024-12-29 13:02:35.254267 +0000 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

frk-00031-00031 2024-12-29 13:02:35.260544 +0000 [ forkit ] WRN  The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to clone dynamic elements of systemplate to the jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585

Expected behavior

The file stash service functions well at port 8334.

Also i noticed that the compose file has changed much from the old one(functions well) i used. But it's so pity i can not find the old docker.yaml.

[F1zzyD]

Same. I tried running this again but pulled the latest docker-compose.yml. Can't get it to start at all. Getting the same errors you are.

[F1zzyD]

So just for fun, I went and looked to see if anyone archived a working compose.yml file using the Wayback Machine, and someone did lol. Plopped it in and it works like normal again. I think the compose file is the only thing wrong since this old one is using the latest docker image.

Either way, here's the docker-compose.yml from the Wayback Machine.

[jeeftor]

I'm unable to get the only office integration working with the latest docker-compose

[jeeftor]

Looks like the latest fixes are switching to COLLABRA - so maybe that's the only office replacement?

[jeeftor]

And unfortunately I'm running into some HTTPs errors with the latest build..

[faywong]

Hasn't start up the docker successfully with the latest docker compose file.

I have rollbacked to use the file-browser in my OMV7 nas.

[F1zzyD]

Hasn't start up the docker successfully with the latest docker compose file.

I have rollbacked to use the file-browser in my OMV7 nas.

I deleted all remnants of Filestash and got it working, fyi

[jeeftor]

Via docker?

I can get FB to run but any docx stuff is broken with an insecure issue

[faywong]

Hasn't start up the docker successfully with the latest docker compose file.
I have rollbacked to use the file-browser in my OMV7 nas.

I deleted all remnants of Filestash and got it working, fyi

Thx for your remind.

I have sudo docker-compose down --rmi all, cleaned all the containers/networks and recreate it, but with no luck.

faywong@faywong-pc:~/docker/filestash$ curl -vv http://localhost:8334
* Host localhost:8334 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
*   Trying [::1]:8334...
* Connected to localhost (::1) port 8334
> GET / HTTP/1.1
> Host: localhost:8334
> User-Agent: curl/8.5.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection
curl: (56) Recv failure: Connection reset by peer
faywong@faywong-pc:~/docker/filestash$ sudo netstat -nlp |grep -i 8334
tcp        0      0 0.0.0.0:8334            0.0.0.0:*               LISTEN      3012740/docker-prox
tcp6       0      0 :::8334                 :::*                    LISTEN      3012746/docker-prox

the compose.yaml i used:

  version: '2'
  services:
    app:
      container_name: filestash
      image: machines/filestash
      restart: always
      ports:
      - "8334:8334"
      volumes:
      - filestash:/app/data/state/

    onlyoffice:
      container_name: filestash_oods
      image: onlyoffice/documentserver
      restart: always
      security_opt:
        - seccomp:unconfined

  volumes:
      filestash: {}

[mickael-kerjean]

with the most recent docker-compose file, you should be able to:

docker-compose up -d

If you use a link like this: http://127.0.0.1:8334/login?type=webdav&url=https://webdav.filestash.app&next=/view/Documents/office.docx you should see: