## TL;DR

Issue browserless/browserless#3245 (closed, 11 comments): Describe the bug This image, which is currently the browserless/chrome:latest, gives me the error The repository 'http://archive.canonical.com/ubuntu kinetic Release' does not have a Release file. for the command RUN apt-get update -y in my Dockerfile To Reproduce Steps to reproduce the behavior: Create a Dockerfile and input the following contents `` FROM browserless/chrome:latest USER root RUN apt-get update -y `` Expected behavior The docker image should be created without any such errors Desktop (please complete the following inform

## Steps

1. Issue browserless/browserless#3245 (closed, 11 comments): **Describe the bug** This image, which is currently the `browserless/chrome:latest`, gives me the error `The repository 'http://archive.canonical.com/ubuntu kinetic Release' does not have a Release file.` for the command `RUN apt-get update -y` in my Dockerfile **To Reproduce** Steps to reproduce the behavior: Create a Dockerfile and input the following contents

``` FROM browserless/chrome:latest USER root RUN apt-get update -y ```

2. **Expected behavior** The docker image should be created without any such errors **Desktop (please complete the following information):** - OS: macOS Ventura 13.3.

3. The failure came from an obsolete Ubuntu partner repository baked into the browserless install. PR #3531 removed it, and the reporter confirmed the latest release installs cleanly again. Update to the release containing that PR and retry the install.

## When to use

Use this skill when you run into "The repository 'http://archive.canonical.com/ubuntu kinetic Release' does not have a Release file".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- http://archive.canonical.com/ubuntu