Skip to content

This PR fix the host not having no permissions over the logs folder - #3

Merged
mmmarinho merged 1 commit into
SmartArmStack:jazzyfrom
ffasilva:logs-folder-permissions-fix
Jul 31, 2026
Merged

This PR fix the host not having no permissions over the logs folder#3
mmmarinho merged 1 commit into
SmartArmStack:jazzyfrom
ffasilva:logs-folder-permissions-fix

Conversation

@ffasilva

Copy link
Copy Markdown

Hi @mmmarinho,

I've added a pre_stop hook to the sas_datalogger_example's compose.yml that gives the host read, write, and execute permissions over the logs folder created by the sas_datalogger_server_container:

# Make the logs fully accessible in the host (i.e., you can read, write, and execute them outside the container)
pre_stop:
  - command: chmod 777 -R /root/logs/

The "owner" and "group" permissions aren't that relevant here since they're inside the container, but the "other users" is what does the trick and makes the folder fully accessible by the host.

The only caveat in this workaround is that the pre-stop hook runs before the stop signal is sent to the container, so the .mat file created by the current execution will still have root-only access. However, this at least lets us easily delete old log files.

Kind regards,
Frederico

… host read, write, and execute permissions to the logs folder
@mmmarinho
mmmarinho merged commit b3c7f62 into SmartArmStack:jazzy Jul 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants