0.16.x Update broke file permissions

[whizzzkid]

Hello Team

My tubesync installation broke the file permissions after 0.16.x update.

Here's my docker compose unit:

  tubesync:
    image: ghcr.io/meeb/tubesync:latest
    container_name: tubesync
    hostname: tubesync
    depends_on:
      - mysql
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - DATABASE_CONNECTION=mysql://root:${MYSQL_PASS}@${MYSQL_HOST}:{MYSQL_PORT}/tubesync
    volumes:
      - ./tubesync:/config
      - ${MOUNT_POINT}/music/youtube:/<mount_path>
      - type: bind
          source: ${RAMDISK}/tubesync
          target: /tmp
          bind:
            create_host_path: true
    ports:
      - "4848:4848"

The files added in the /<mount_path> after the update seems to have permissions of 644 instead of 755 that I expected (and was the norm before). Not sure what changed, but will revert to 0.15 till this is figured out.

[tcely]

Is this something under /downloads?

tubesync/config/root/etc/s6-overlay/s6-rc.d/tubesync-init/run

Lines 22 to 42 in b188dcb

	# Reset permissions
	chown -R app:app /run/app
	chmod -R 0700 /run/app
	chown -R app:app /config
	chmod -R 0755 /config
	chown -R root:app /app
	chmod -R 0750 /app
	chmod 0755 /app/*.py /app/*.sh
	find /app -mindepth 2 -type f -execdir chmod 640 '{}' +
	chown -R app:app /app/common/static
	chown -R app:app /app/static
	# Optionally reset the download dir permissions
	if [ "${TUBESYNC_RESET_DOWNLOAD_DIR:=True}" == "True" ]
	then
	export TUBESYNC_RESET_DOWNLOAD_DIR
	echo "TUBESYNC_RESET_DOWNLOAD_DIR=True, Resetting /downloads directory permissions"
	chown -R app:app /downloads
	chmod -R 0755 /downloads
	fi

[whizzzkid]

@tcely I am not sure I understand the question.

[tcely]

My tubesync installation broke the file permissions after 0.16.x update.

That doesn't say what files you are writing about. You actually didn't write which specific version you tried either. Was it v0.16.2 or v0.16.1?

• ${MOUNT_POINT}/music/youtube:/<mount_path>

That bind mount looks like nonsense. Did you redact something?

The files added in the /<mount_path> after the update seems to have permissions of 644 instead of 755 that I expected (and was the norm before).

Again with the /<mount_path> nonsense.

If the actual mount point is /downloads then, chown -R app:app /downloads ; chmod -R 0755 /downloads running would change files to 0755 every time the container starts, unless you set TUBESYNC_RESET_DOWNLOAD_DIR to False.

Please provide some useful details about what you are seeing. Include logs from the container that you are seeing trouble with.

Your compose might be replaced with something more reasonable:

services:
  tubesync:
    image: ghcr.io/meeb/tubesync:latest
    container_name: tubesync
    hostname: tubesync
    depends_on:
      - mysql
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - DATABASE_CONNECTION=mysql://root:${MYSQL_PASS}@${MYSQL_HOST}:${MYSQL_PORT}/tubesync
    volumes:
      - ./tubesync:/config
      - ${MOUNT_POINT}/music/youtube:/downloads
      - ${RAMDISK}/tubesync:/tmp
    ports:
      - "4848:4848"

[github-actions]

The issue has been closed due to no response from the author. Responses, from the original author of the issue, should automatically re-open the issue.