Skip to content

Fix IPFS-hash workflow build failure from missing Tailscale image tag#38

Draft
Pol-Lanski with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-github-actions-job
Draft

Fix IPFS-hash workflow build failure from missing Tailscale image tag#38
Pol-Lanski with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-github-actions-job

Conversation

Copilot AI commented Jun 3, 2026

Copy link
Copy Markdown

The Build and post IPFS hash GitHub Actions job failed because the build referenced a non-existent upstream image tag (tailscale/tailscale:v1.98.5). This PR repoints the package to an available upstream tag so the CI build step can resolve its base image.

  • Root cause

    • CI build pulled tailscale/tailscale:v1.98.5, which is not published on Docker Hub.
  • Change

    • Downgraded the pinned upstream Tailscale version from v1.98.5 to v1.98.4 in:
      • dappnode_package.json (upstreamVersion)
      • docker-compose.yml (build.args.UPSTREAM_VERSION)
  • Impact

    • Keeps Dockerfile/image resolution aligned with a published upstream tag used by the workflow build path.
# docker-compose.yml
services:
  tailscale:
    build:
      args:
        UPSTREAM_VERSION: v1.98.4

Copilot AI changed the title [WIP] Fix failing GitHub Actions job Build and post IPFS hash Fix IPFS-hash workflow build failure from missing Tailscale image tag Jun 3, 2026
Copilot AI requested a review from Pol-Lanski June 3, 2026 08:09
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 585a576

This is a development version and should only be installed for testing purposes.

  1. Package tailscale.dnp.dappnode.eth

Install link

Hash: /ipfs/Qmf1CVsAKiCNmZC68sLTZUypgw9XEcA5XHXkitPhZHuXWr

(by dappnodebot/build-action)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants