I'm trying to get smr running on my Fedora Linux 42 laptop and I'm running into problems. I've tried with SELinux enforcement on and off and it doesn't seem to matter one way or the other:

[qdnqn]

I'm trying to get smr running on my Fedora Linux 42 laptop and I'm running into problems. I've tried with SELinux enforcement on and off and it doesn't seem to matter one way or the other:

$ smrmgr start

================================================================================================
Node Information
================================================================================================
Agent name:           simplecontainer-node-1
Domain:               localhost
Image:                quay.io/simplecontainer/smr
Tag:                  v0.1.99
IP Address:           'auto-detected'
Join cluster:         false
Peer address:         'N/A'
Service install:      false
smr version:          v0.1.98
smrctl version:       v0.0.128
================================================================================================

Log files:
  Cluster: tail -f /home/fozz/nodes/simplecontainer-node-1/logs/cluster.log
  Control: tail -f /home/fozz/nodes/simplecontainer-node-1/logs/control.log
================================================================================================
[2025-09-19 14:17:45] [INFO] Creating node with arguments: --image quay.io/simplecontainer/smr --tag v0.1.99 --node simplecontainer-node-1 --listen 0.0.0.0:1443 --domain localhost
config created and saved at /home/fozz/nodes/simplecontainer-node-1/config/config.yaml
[2025-09-19 14:17:45] [INFO] Node 'simplecontainer-node-1' created successfully
[2025-09-19 14:17:45] [INFO] Starting node: simplecontainer-node-1
starting node with the user: 1000:1000
node started
connection failed after retries: Get "https://localhost:1443/connect": dial tcp [::1]:1443: connect: connection refused
[2025-09-19 14:17:55] [ERROR] Failed to start node

Can you advise me on how to troubleshoot this?

Originally posted by @fozzmoo in #24 (comment)

[qdnqn]

Hi @fozzmoo,

I've moved it to the issues.

The most common issue is access from the simplecontainer node container to the /var/run/docker.sock.

Invalid access will prevent the node container from starting. You can confirm this with: docker logs simplecontainer-node-1 in your case. Anything in the logs related to the /var/run/docker.sock will confirm that it is the reason.

I've released a new fix for this. The container will pick up all the groups the current user has and append them to the container.

The proper solution is to add the current user to the docker group so they have access to /var/run/docker.sock. As a quick workaround, you can temporarily change the ownership of /var/run/docker.sock to the current user.

To set the current user to have correct access to the /var/run/docker.sock, you can follow the instructions at the following URL: https://docs.simplecontainer.io/installation/debugging

If the docker ps works correctly on your system, everything is configured correctly, and there is no need to do anything. Just run the commands below to update smr and smrctl and rerun the start of the node.

To run with success:

sudo smrmgr install 
smrmgr start

If this is not the case, please also check the prerequisites: https://docs.simplecontainer.io/installation/prerequisites

Hope this helps.