Unused `tv` folder created

[vdrover 62]

I use docker to run Emby on my Ubuntu 24.04 system. Here are the volumes I mount in my compose file: 

      - $DATADIR/emby/movies:/data/movies
      - $DATADIR/emby/tv:/data/tvshows

As expected, `movies` and `tv` folders appear on my system in the `DATADIR` folder.

I want to move my tv library to another disk. So, I decided to simply map the same `/data/tvshows/` emby library to a new location. I shut down my containers, moved the tv files to my new location, deleted the original `tvshows` folder, and updated my compose file as follows:

      - $DATADIR/emby/movies:/data/movies
      - $TVDIR:/data/tvshows

After restarting my Emby container, I inspected my library settings in Emby and `/data/tvshows` was still selected. I also tried playback of existing shows as well as recording new shows. As expected, everything was working with the new location for the tv library, `TVDIR`. 

The only thing that was unexpected was that an empty, apparently unused `tv` folder was recreated in the original location, i.e. `$DATADIR/emby/tv`. It seems harmless, but it's a bit untidy. Any thoughts on how to remove this legacy library folder so it's not recreated when the Emby container restarts?

Edited June 25, 2024 by vdrover

[Luke 42080]

Hi, did you try deleting it?

[vdrover 62]

Yes, it reappears on each restart.

[Luke 42080]

Yea that's odd. Maybe the server log will shed some light.

[Q-Droid 989]

I think some relevant info is missing here. Normally the container would not have access to storage beyond what's specified in the bind mounts. Unless the new TVDIR path is part of the old DATADIR path (or the other way around) OR you are using an SMB/UNC path as an additional shared network folder for the library.

 

[vdrover 62]

I solved the issue: I was mapping the `tv` folder to another container. In otherwords, no bug in Emby