Transcoding folder does not have write permission

[tbutz12 0]

When using the feature to add a custom transcode folder, the repo binhex-emby does not add write permission to the custom selected folder via PATH mapping on the container. Example:

When using the above path, and in emby doing a search for the folder under transcoding results in:

To prevent this issue, I created a script that runs on startup that will add this permission. However, I think this might be a bug.

Edited December 30, 2024 by tbutz12
Picture did not come through

[Neminem 1518]

I have been using ram drive to transcode.

But it was a mess, when some stream ran wild,

or grandma forgot to step back from live tv show, and just turned of the TV and not her firetv stick.

Those transcodes would eat up my ram and impact my server in not so funny ways.

At least you use /shm and not /tmp.

/shm only allocates half you ram.

 

In stead I use and old scrap ssd that I don't need. 

In my opinion you should stay away from ram drives when using emby.

[Luke 42077]

Hi, have you tried our official docker container?

[tbutz12 0]

Yes. It happens on both. 

[Gocco 0]

我和你一样，也是文件夹权限的问题

[Neminem 1518]

If you really want to go down this road. 

!! You have be warned !!

This should apply to Emby also.

 

[Luke 42077]

19 hours ago, tbutz12 said:

Yes. It happens on both. 

How did you configure the docker volumes?