IPFS Daemon Not Accessible

[RobotSail]

After installing IPFS for rootless containers via containerd-rootless-setuptool.sh -- install-ipfs --init, the service's logs show that the IPFS daemon has launched and is running in the background.
However, making requests to IPFS doesn't work and running netstat -tulpn 4001 produces no results. Additionally, I'm able to start the regular IPFS daemon without issue, and only then do nerdctl pull ipfs://cid commands sort of work, at least without producing a
FATA[0000] ipfs api address could not be found error.

I've already had IPFS installed on my system, so this may have helped to cause the issue.

[AkihiroSuda]

nerdctl/extras/rootless/containerd-rootless-setuptool.sh

Line 441 in 354d03a

INFO "If you want to expose the port 4001 of ipfs daemon, re-install rootless containerd with CONTAINERD_ROOTLESS_ROOTLESSKIT_FLAGS=\"--publish=0.0.0.0:4001:4001/tcp\" environment variable."

Please try creating ~/.config/systemd/user/containerd.service.d/override.conf

[Service]
Environment="CONTAINERD_ROOTLESS_ROOTLESSKIT_FLAGS=--publish=0.0.0.0:4001:4001/tcp"

[AkihiroSuda]

Sorry typo

[Service]
Environment="CONTAINERD_ROOTLESS_ROOTLESSKIT_FLAGS=--publish=0.0.0.0:4001:4001/tcp"

[RobotSail]

Thanks, that seems to have fixed my problem with containerd. Now when I try pulling images with the ipfs:// prefix, I run into this error:

~❯  nerdctl run -it ipfs://bafkreicq4dg6nkef5ju422ptedcwfz6kcvpvvhuqeykfrwq5krazf3muze echo hello                                                                                                                              
FATA[0000] ipfs api address could not be found          

Running netstat -tulpn shows no IPFS ports open besides 4001:

~❯  sudo netstat -tulpn                                                                                                                                                                                                        Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1269/cupsd          
tcp        0      0 127.0.0.1:36905         0.0.0.0:*               LISTEN      1628/docker-proxy   
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      1084/systemd-resolv 
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      1084/systemd-resolv 
tcp6       0      0 :::4001                 :::*                    LISTEN      8064/rootlesskit    
tcp6       0      0 ::1:631                 :::*                    LISTEN      1269/cupsd          
tcp6       0      0 :::5355                 :::*                    LISTEN      1084/systemd-resolv 
udp        0      0 0.0.0.0:37242           0.0.0.0:*                           8093/slirp4netns    
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           8402/chrome --enabl 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           8402/chrome --enabl 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1111/avahi-daemon:  
udp        0      0 0.0.0.0:5355            0.0.0.0:*                           1084/systemd-resolv 
udp        0      0 0.0.0.0:54775           0.0.0.0:*                           1111/avahi-daemon:  
udp        0      0 127.0.0.53:53           0.0.0.0:*                           1084/systemd-resolv 
udp        0      0 127.0.0.1:323           0.0.0.0:*                           1227/chronyd        
udp6       0      0 :::35439                :::*                                1111/avahi-daemon:  
udp6       0      0 :::5353                 :::*                                1111/avahi-daemon:  
udp6       0      0 :::5355                 :::*                                1084/systemd-resolv 
udp6       0      0 ::1:323                 :::*                                1227/chronyd        

But the output of systemctl --user status ipfs-daemon.service indicates that the service is healthily running with no issues, and the log output is exactly what I would expect from a typical IPFS startup:

● ipfs-daemon.service - ipfs daemon for rootless nerdctl
     Loaded: loaded (/home/oleg/.config/systemd/user/ipfs-daemon.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2022-03-10 10:49:29 EST; 6min ago
   Main PID: 8131 (ipfs)
      Tasks: 16 (limit: 18866)
     Memory: 205.1M
        CPU: 1min 2.815s
     CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/ipfs-daemon.service
             └─8131 ipfs daemon --init

Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip4/10.0.2.100/udp/4001/quic
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip4/108.20.160.75/udp/37242/quic
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip4/127.0.0.1/tcp/4001
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip4/127.0.0.1/udp/4001/quic
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip6/::1/tcp/4001
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Swarm announcing /ip6/::1/udp/4001/quic
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: API server listening on /ip4/127.0.0.1/tcp/5888
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: WebUI: http://127.0.0.1:5888/webui
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/5889
Mar 10 10:49:30 fedora containerd-rootless-setuptool.sh[8131]: Daemon is ready

[AkihiroSuda]

Cc @ktock

[ktock]

@RobotSail Does IPFS_PATH point to ~/.local/share/ipfs?

[RobotSail]

@ktock Bash and Zsh were already pointing to it. I just set fish to point there as well and restarted the ipfs service via systemctl but to no luck.