Jump to content

Emby container on docker /portainer set as private


Go to solution Solved by CassTG,

Recommended Posts

Posted

Hello!

I had issues with my emby container not seeing one of my folders so I recreated it to investigate. Bad luck I set it to private (not administrators) so i can't access it or freeing the ports (You'll see i've tried to create another instance). Last but not least i'm not at home but i can access my openmediavault server. I know it's more about docker than emby but i didn't find how to set it to administrators or reinstall from scratch docker on openmediavault 6 alpha.

To make it short i want to remove cool_borg.

Thank you for your help!

privatecontainer.png

Posted (edited)

In portainer:

  • Click on the faulty docker
  • 2nd box down is access control so click on change ownership
  • set to admin

That should do it

Screenshot 2021-10-31 at 10.27.56.png

Edited by CassTG
Posted (edited)

Thank you @CassTG

I couldn't do it.

I purged docker-ce and reinstalled it.  I re-created emby from scratch but portainer says "ports 8096 and 8920 are already allocated". I don't know how to free my ports because the only containers i see are portainer and emby.

 

grep 8920.png

Edited by gretagarbo
added output of grep 8920 (same for 8096)
Posted (edited)

Are you setting your dockers up on Host Network? 

As Creating a custom bridge network is seriously the best way forward

I presume you are not running behind a proxy ssl but going direct?

You could technically just map different ports as a worst case if you cant wipe the server

i.e map 8921:8920 that way public access is via port 8921 which maps internally to emby as 8920 and then change the public port in Emby settings itself

whats the output of

docker container ls --all

Also after you purged docker did you remove the folder below which is where all images volumes etc are contained just to make sure.

Obviously doing this will wipe everything so if you done a scan in emby it would start a fresh

Quote

WARNING - this deletes everything images, volumes all data etc so only do if you are happy starting a fresh

sudo rm -rf /var/lib/docker

If you did do a scan you could backup your emby data volume folder and move out of this folder to root temporarily then move back once you reinstall docker

Edited by CassTG
Posted

Also silly question but did you reboot after nuking docker just incase and try that netstat command again

Posted
Quote
sudo rm -rf /var/lib/docker

I had forgotten this line. I'm going to test now

Thank you

  • Solution
Posted

I would Remove Docker as per their instructions then execute the comand above

Reboot and check the netstat command again before reinstalling

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...