plugs issue

v2: Troubleshooting
1

Hi there!

I am struggling with plugs since I updated to v2, and I hope you can help.

I am running silverbullet v 2.1.9-0 (the one from docker, ghcr.io image, tag latest) on an arm64 system. I tried both treeview and graphview plugs and I have network issues below:

silverbullet_v2  | 2025/10/21 20:51:29 Proxying to https://raw.githubusercontent.com/joekrill/silverbullet-treeview/main/treeview.plug.js
silverbullet_v2  | 2025/10/21 20:51:29 Error fetching proxied URL: Get "https://raw.githubusercontent.com/joekrill/silverbullet-treeview/main/treeview.plug.js": dial tcp: lookup raw.githubusercontent.com on 127.0.0.11:53: server misbehaving
silverbullet_v2  | 2025/10/21 20:53:37 Proxying to https://api.github.com/repos/deepkn/silverbullet-graphview/releases/latest
silverbullet_v2  | 2025/10/21 20:53:37 Error fetching proxied URL: Get "https://api.github.com/repos/deepkn/silverbullet-graphview/releases/latest": dial tcp: lookup api.github.com on 127.0.0.11:53: server misbehaving

Is this a known problem? do you think there is an issue with the docker alpine image?

thank you in advance for any hints!

2

Is your arm machine, more specifically your docker container able to reach the internet?

3

Hi ! thanks for the suggestion. I added a public DNS inside the container and I am indeed able to fetch the plugs..

Problem now is that every time I restart the container, I have the issue again (the DNS change is not persistent). I am now trying to understand if this is a docker issue on my side… Though all my other containers are working properly.

Michele

4

How are you launching the container and how did you configure the dns?

5

for running it I have a compose file which does not do anything special related to networking… like this:

  silverbullet_v2:
    container_name: silverbullet_v2
    image: ghcr.io/silverbulletmd/silverbullet:latest
    environment:
    - SB_USER=user:pass
    restart: unless-stopped
    volumes:
      - ./space:/space
    ports:
      - "3133:3000"

It is definitely a problem specific to my setup, as I tested the container on another arm64 machine and it is indeed resolving DNS from the inside…

on the docker network side, docker network ls shows a bridged network, as expected. This is the output of the inspect command:

[
    {
        "Name": "silverbullet_v2_default",
        "Id": "fdd8570a9fe63b4567dc3046ff612f0918f650de6f238d97067",
        "Created": "2025-10-21T20:33:49.836189597Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "192.168.96.0/20",
                    "Gateway": "192.168.96.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "13f5e0e0de3fe0bde5dca2acc510f0e4f697dbc19ba4104": {
                "Name": "silverbullet_v2",
                "EndpointID": "2301380b2d2edfef73d10d924f1d8e2b5c0ee5fa84d3f543f6f2",
                "MacAddress": "aa:99:71:f7:b0:f5",
                "IPv4Address": "192.168.96.2/20",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {
            "com.docker.compose.config-hash": "ae08a823475c0f3e50d1e6442d49d292584a9c2e3a2acf925c",
            "com.docker.compose.network": "default",
            "com.docker.compose.project": "silverbullet_v2",
            "com.docker.compose.version": "2.39.3"
        }
    }
]

The host resolves DNS correctly so I would not investigate too much there…

6

Can you run e.g.

docker exec -it silverbullet_v2 wget https://community.silverbullet.md/t/plugs-issue/3434

Does this resolve?

If it doesn’t, it’s probably a DNS issue in the container, which I’m no expert for and if it does, it’s probably a DNS issue with SB which I’m no expert for …

7

if I edit /etc/resolv.conf in the container wget works, but it does not as soon as I restart the container.

So I should definitely have a look at what docker does before running it. Thanks for your help!

8

I resolved it with CONTAINER_BOOT for the time being. I will then investigate more

1 Like