[Filebot Node] How can i set -no-xattr?

[howdymilsap]

how do you set -no-xattr in the filebot node interface?

[rednoah]

1.
Why do you want to turn off xattr? Did you run into any specific issue? Care to elaborate? AFAIK, all Synology devices support xattr just fine.


2.
Unfortunately, FileBot Node does not have a checkbox that corresponds to this option.

[howdymilsap]

I don't use this on synology, I use the docker filebot node with an rclone mounted filesytem. The destination filesystem doesn't currently support xattr and so I see a lot of error messages in the log. I realize I can just ignore them, but was hoping I could use the -no-xattr option to eliminate them.

btw, the node implementation is pretty flawless. Amazing work. Thanks.

[rednoah]

I see. You should be able to disable the xattr feature by setting the FILEBOT_OPTS environment variable as follows:

Code: Select all

export FILEBOT_OPTS="-DuseExtendedFileAttributes=false"

I'm no docker expert, but you should be able to set environment variables via the command-line or configuration or docker file or something.

[howdymilsap]

This solution works perfectly. Thanks again.

[rednoah]

I'd appreciate it if you could share how you implemented this solution, for the next guy that stumbles on this thread.

[howdymilsap]

I'd appreciate it if you could share how you implemented this solution, for the next guy that stumbles on this thread.

I use portainer to manage my docker containers. To fix this issue, I just modified your standard container in the portainer GUI and updated the existing FILEBOT_OPTS environment variable to be the following:

Code: Select all

	-Dapplication.deployment=docker -Duser.home=/data -DuseExtendedFileAttributes=false

I then simply re-deployed the container and the new configuration was in place. I will create an automated deploy for this container (with my modification) to this using Ansible, and will post that script here once I have a bit more time.

[dyl4n20]

I'd appreciate it if you could share how you implemented this solution, for the next guy that stumbles on this thread.

I use portainer to manage my docker containers. To fix this issue, I just modified your standard container in the portainer GUI and updated the existing FILEBOT_OPTS environment variable to be the following:

Code: Select all

	-Dapplication.deployment=docker -Duser.home=/data -DuseExtendedFileAttributes=false

I then simply re-deployed the container and the new configuration was in place. I will create an automated deploy for this container (with my modification) to this using Ansible, and will post that script here once I have a bit more time.

i am trying to replicate this and I don't understand how you added the environment variables in portainer.

[rednoah]

Making your own container is an unnecessarily complicated way to set environment variables. I see no need or reason for doing it this way.


useExtendedFileAttributes=false can be set via a configuration file. See xattr metadata for details.


You can use docker to set environment variables. Every docker management UI has configuration text fields for this.