spinnaker: I could not install spinnaker on ubuntu 20.4
Issue Summary:
I 'm trying to install spinnaker on ubuntu 20.4 according https://spinnaker.io/docs/setup/install/deploy/ and I get the following error:
- Run
hal deploy connectto connect to Spinnaker. Updating apt package lists… Hit:1 http://by.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://by.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://by.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://by.archive.ubuntu.com/ubuntu focal-security InRelease Hit:5 http://ppa.launchpad.net/chris-lea/redis-server/ubuntu focal InRelease Hit:6 https://download.docker.com/linux/ubuntu focal InRelease Hit:7 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease Err:8 https://dl.bintray.com/spinnaker-releases/debians focal InRelease 403 Forbidden [IP: 54.69.109.244 443] Reading package lists… E: Failed to fetch https://dl.bintray.com/spinnaker-releases/debians/dists/focal/InRelease 403 Forbidden [IP: 54.69.109.244 443] E: The repository ‘https://dl.bintray.com/spinnaker-releases/debians focal InRelease’ is not signed. ! ERROR Error encountered running script. See above output for more details.
Cloud Provider(s):
on-prem
Environment:
Ubuntu 20.04 LTS any versions of spinnaker(
- 1.19.14 (Gilmore Girls A Year in the Life): Changelog: https://gist.github.com/spinnaker-release/cc4410d674679c5765246a40f28e3cad Published: Thu Aug 13 23:44:46 UTC 2020 (Requires Halyard >= 1.32)
- 1.20.7 (Drive to Survive): Changelog: https://gist.github.com/spinnaker-release/75d50c7b931f1089e710a0e9d1acf8c4 Published: Wed Jul 22 22:22:44 UTC 2020 (Requires Halyard >= 1.32)
- 1.21.5 (Dark): Changelog: https://gist.github.com/spinnaker-release/98c3bab183b507662a8f5524e54626d4 Published: Mon Dec 07 23:09:05 UTC 2020 (Requires Halyard >= 1.32)
- 1.22.6 (Anne): Changelog: https://gist.github.com/spinnaker-release/e457272b5aac37a5c6512b80b0c53d5f Published: Thu Jan 28 02:11:57 UTC 2021 (Requires Halyard >= 1.32)
- 1.23.7 (Hemlock Grove): Changelog: https://gist.github.com/spinnaker-release/94280a2b615adccd975eed73359023ac Published: Fri Feb 19 01:25:30 UTC 2021 (Requires Halyard >= 1.32.0)
- 1.24.6 (Queen’s Gambit): Changelog: https://gist.github.com/spinnaker-release/25abcd046795c6f34bb2d8d4977f0415 Published: Thu Jul 01 20:40:34 UTC 2021 (Requires Halyard >= 1.32)
- 1.25.7 (Chilling Adventures of Sabrina): Changelog: https://gist.github.com/spinnaker-release/83c1a4069029bfd79d11ad8e8bf1d326 Published: Fri Jul 02 21:23:23 UTC 2021 (Requires Halyard >= 1.41)
- 1.26.6 (Disenchantment): Changelog: https://gist.github.com/spinnaker-release/e3714a97bbdd3e7c3b4d92adec938e7f Published: Thu Jul 01 00:49:04 UTC 2021 (Requires Halyard >= 1.41) )
Feature Area:
Description:
Steps to Reproduce:
Additional Details:
Please delete the instructions below this line prior to submitting
Instructions:
- An issue is not a place to ask questions. Please use Slack or Stack Overflow.
- Before you open an issue, please check if a similar issue already exists or has been closed before.
- Make sure you have read through the Spinnaker FAQ and Halyard FAQ to provide as much information as possible.
Descriptions:
- Issue Summary: A brief description of what you’re seeing.
- Cloud Provider: AWS, GCP, Kubernetes, Azure, Cloud Foundry, etc. Please assign a label from the right so your issue can be properly sorted.
- Environment: As much information about your Spinnaker environment and configuration that might be relevant to the issue. For example: “I am running Spinnaker using the Amazon images to deploy into AWS and GCP.”
- Feature Area: Notifications, Pipelines, UI, Jenkins, etc. Please assign a label from the right so your issue can be properly sorted.
- Description: The behavior you expect to see, and the actual behavior.
- Steps to reproduce: Ideally, an isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem). If not possible, as much information as possible to see this behavior.
- Additional Details: Additional information such as screenshots and exception logs.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 7
- Comments: 15 (1 by maintainers)
In some sense the root cause is that bintray is gone (https://status.bintray.com/). The current build process doesn’t publish debian packages so the combination of those things means halyard with
LocalDebianhas a hard time.I really hope this won’t be treated as any kind of advertisement/etc. I needed to install Spinnaker for testing/trial purposes only, but faced this issue with inaccessible debian repos. So ended up with docker-compose solution. Not providing any links, but in case you are interested - you can find spin-brewery repo in my acc.