Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interfering with existing SMB shares #63

Closed
jconly opened this issue Oct 17, 2019 · 1 comment
Closed

Interfering with existing SMB shares #63

jconly opened this issue Oct 17, 2019 · 1 comment

Comments

@jconly
Copy link

jconly commented Oct 17, 2019

Hi, please forgive any ignorance. Relatively new to Docker.
I recently did a fresh pull and run of the image, and it seems the container is now interfering with my already existing Samba server on the host machine. Any advice?

Thank you. Thinks have been working great so far!

@odarriba
Copy link
Owner

That´s the expected behaviour, since we are migrating to SMB shares (you can see more info on #58), so it will be using the same port as your samba server and probably intefering with it.

Your best chance is to use an older image of the AFP protocol, or switch to another docker container that doesn't use SMB.

However, Apple is actively witching to SMB and that´s probabley the way to go. Maybe you can even configure the TimeMachine endpoint on your existing SMB server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants