1

Are you using stock Docker compose setup? Yes / At least I’m trying to

Describe the problem you’re having:
I’m trying to install on a new server running Debian 11 . I’ve got Docker version 20.10.5+dfsg1, build 55c4c88 installed and I think it is working ok. By this, I mean I can run the hello world container, and a few other containers with no errors.

Things appear to go ok, but I can’t start all the tt-rss containers.

Creating ttrss-docker2_db_1 … done
Creating ttrss-docker_backups_1 … error
Creating ttrss-docker_app_1 … done
Creating ttrss-docker_updater_1 …
Creating ttrss-docker_web-nginx_1 …
Creating ttrss-docker_updater_1 … error
Creating ttrss-docker_web-nginx_1 … done

ERROR: for ttrss-docker_updater_1 Cannot start service updater: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: “/opt/tt-rss/updater.sh”: permission denied: unknown

ERROR: for backups Cannot start service backups: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: “/opt/tt-rss/dcron.sh”: permission denied: unknown

ERROR: for updater Cannot start service updater: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: “/opt/tt-rss/updater.sh”: permission denied: unknown

I end up with the web, db, and app servers running ok, but the backup and updater don’t start.

…

Include steps to reproduce the problem:
Here’s what I do (I’ve tried a few times with the same result):

  • I get the docker files with a git clone(git clone ttrss-docker-compose.git - ttrss-docker) – this works ok
  • cd into the directory that just got made (cd ttrss-docker)
  • I copy .env-dist to .env
  • I look at the file and decide to not make any changes
  • I run docker-compose build (no errors)
  • I run docker-compose up (errors. see above)

…

tt-rss version (including git commit id):
n/a
…

Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
Debian 11 / Docker version 20.10.5+dfsg1, build 55c4c88 installed
…

Please provide any additional information below:
I dunno. This is at such a basic level with the containers that on one hand I feel like it’s gotta be a docker issue. On the other, I guess anything is possible and the couple other containers I’ve tried to run all appear to work normally. I wish I had another machine to try this on, but I don’t

Thanks in advance for the help.

[I edited for some formatting issues]
…

2

Do the scripts mentioned have their executable bit set?

ls -nl ttrss-docker/app/*.sh

3

well, this is embarrassing. They haven’t got it set for some reason. I can’t believe I didn’t think to look there. So we’ve found the problem… Thanks

I’ve got something else to sort out though…for some reason I can’t chmod them to be executable. I’ll sort that out

I thought I would add that I’ve reran the git to another location on my computer and checked the scripts. They have the execute bit properly set. I’ve got something funky unrelated to ttrss going on. Thanks again for the help