heroku / heroku/cli

container:push error when Docker containerd enabled

Open
#3,222 2 comments 0 reactions 0 assignees View on GitHub
on-call reviewed
Dominant language
TypeScript
Stars
889
Forks
236
Avg merge
2d 10h
Merged PRs (30d)
33

Description

We bumped into this when someone new joined the team, and this setting inside Docker was enabled for new installations but not for everyone else:

![Image](https://github.com/user-attachments/assets/1409e08b-4afa-4e98-8fe1-3004ddb6d85e)

When doing `heroku container:push -a APP web` we see this error, and the only way around it we've discovered is turning off this rather obscure setting in Docker. It took quite a while to track this cause down.

Image

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.