Coder Social home page Coder Social logo

Comments (4)

tadly avatar tadly commented on June 7, 2024 4

Okay, one more update.

I wasn't aware that rpcbind is basically part of nfs.
On ubuntu systems, nfs-common seems to be pre-installed which also installes and enables rpcbind.

As such docker-nfs silently fails in host-mode or complains when trying to bind to 111.

Solution: Either remove nfs-common if you don't need it or systemctl mask rpcbind

from docker-nfs-server.

flebel avatar flebel commented on June 7, 2024 3

Solution: Either remove nfs-common if you don't need it or systemctl mask rpcbind

On top of systemctl mask rpcbind, I also had to:

systemctl stop rpcbind.socket
systemctl disable rpcbind.socket

from docker-nfs-server.

ehough avatar ehough commented on June 7, 2024

Hello and my apologies for the super-long delay in responding.

A quick look at your docker-compose.yml indicates that you perhaps forgot to expose the container ports. i.e. it should look something like this:

version: '3'

services:
  nfs:
    container_name: nfs
    image: erichough/nfs-server:latest
    network_mode: 'host'
    privileged: true
    volumes:
      # Config
      - '/docker/data/nfs/exports:/etc/exports:ro'
      # Shares
      - '/mnt/Backups:/Backups'
      - '/mnt/Documents:/Documents'
      - '/mnt/Multimedia:/Multimedia'
    restart: unless-stopped

    # THESE LINES ARE MISSING ...
    # vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    ports:
      - 2049:2049
      - 2049:2049/udp
      - 111:111
      - 111:111/udp
      - 32765:32765
      - 32765:32765/udp
      - 32767:32767
      - 32767:32767/udp

Give that a try?

from docker-nfs-server.

tadly avatar tadly commented on June 7, 2024

No worries and thanks for getting back to me.

I am using network_mode: 'host' though so I really shouldn't need that.
I tested anyways (removing host mode) and as expected I have the exact same issue.

Edit:
I just figured out the issue. It's rpcbind which runs on port uses port 111.
If I start the container in host mode, nothing ever complains but silently fails to bind to that port.

When testing earlier using port-mapping I used non-existing nfs-paths as I restructured some stuff some time ago.

from docker-nfs-server.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.