Task #5304
closed
Change default Unix socket path to /run/nfd/nfd.sock
100%
Description
Presently, NFD creates the Unix socket at /run/nfd.sock.
This causes difficulty in NFD Docker packaging: either the container must mount /run in read-write mode which gives the container too much privilege, or the client.conf must be edited to point to a different socket path.
This issue is to change the default Unix socket path path to /run/nfd/nfd.sock, without any backwards compatibility.
NFD must create the enclosing directory if it does not exist.
Updated by Davide Pesavento 5 months ago
- Tags changed from approved to approved, docker, systemd
- Subject changed from Change Unix socket path to /run/nfd/nfd.sock to Change default Unix socket path to /run/nfd/nfd.sock
FWIW, moving the socket file to a subdir will also enable running NFD as a systemd service without full root privileges.
Updated by Davide Pesavento 4 months ago
- Tracker changed from Feature to Task
- Status changed from New to In Progress
- Assignee changed from Varun Patil to Davide Pesavento
- % Done changed from 0 to 50
Updated by Davide Pesavento 4 months ago
- Status changed from In Progress to Code review
Updated by Davide Pesavento 4 months ago
- Status changed from Code review to Closed
- % Done changed from 50 to 100
Updated by
Updated by Junxiao Shi 4 months ago
NDNts has supported the new socket path, with limited backwards compatibility, in this commit:
https://github.com/yoursunny/NDNts/commit/0b748bf7d67580d3a07ed2cdd3a9590b5fdacdf1
Mini-NDN is possibly broken according to this complaint:
https://www.lists.cs.ucla.edu/pipermail/nfd-dev/2024-January/004555.html
ppa-packaging has a copy of nfd.conf with old socket path.
This affects NFD-nightly: nfdc would attempt to connect to new socket path, while nfd listens on old socket path.
Updated by Junxiao Shi 3 months ago
https://gerrit.named-data.net/c/ppa-packaging/+/7347 nfd.conf in ppa-packaging