Skip to content

VM can't contact GitHub in IPv6 only environments #270

@SchoolGuy

Description

@SchoolGuy

Bug Report

Description

When hosting Fireactions in an IPv6 only environment, operation is not possible because the VM has no IPv6 address assigned and no IPv4 network is available.

Expected Behavior

The VM can contact GitHub.

Current Behavior

Logs from the runner VM

Oct 17 00:21:43 localhost.localdomain systemd[1]: Started Fireactions.
Oct 17 00:21:43 localhost.localdomain fireactions[850]: 2025-10-17 00:21:43 INF runner.go:113 > Starting GitHub runner
Oct 17 00:21:43 localhost.localdomain fireactions[850]: 2025-10-17 00:21:43 INF runner.go:114 > Running command: /opt/runner/run.sh
Oct 17 00:41:05 localhost.localdomain fireactions[903]: 2025-10-17 00:41:05Z: Runner connect error: Resource temporarily unavailable (pipelinesghubeus22.actions.githubusercontent.com:443). Retrying until reconnected.

IP address:

root@localhost:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2e:1e:e0:2c:02:74 brd ff:ff:ff:ff:ff:ff
    inet 192.168.128.2/24 brd 192.168.128.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::2c1e:e0ff:fe2c:274/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 72:ab:ed:b8:b9:22 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

Possible Solution

None available atm

Steps to Reproduce (for bugs)

  1. Use Ansible Playbook to install
  2. Minor tweaks not covered by the Ansible Playbook (downloading kernel and setting up the lvm thin pool)
  3. Starting the fireactions systemd service
  4. Login to a VM

Your Environment

  • Fireactions version: 0.3.0
  • OS: openSUSE Leap 15.6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions