Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

rootless installation failing on Raspberry PI

Open
#343 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, shell
Domain
devops

Research direction

Start with the rootless installation script invoked by https://get.docker.com/rootless and reproduce the failure on the Raspberry Pi environment described. Trace how it turns uname -m's armv7l into the download URL, then verify that installation completes using the available armhf target.

Written by the indexing model from the issue text.

Description

Running

curl -sSL https://get.docker.com/rootless | sh

returns (= fails)

# Installing stable version 23.0.0
# Executing docker rootless install script, commit: 6647403
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 379 100 379 0 0 1162 0 --:--:-- --:--:-- --:--:-- 1166
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 395 100 395 0 0 1362 0 --:--:-- --:--:-- --:--:-- 1362

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

The cause seems to be that uname -m resolves to armv7l which is not available at https://download.docker.com/linux/static/stable/

Note that dpkg --print-architecture, which is used to set up apt-get would resolve to armhf

Environment: Raspberry PI 2 B, Raspberry PI OS light, 32 bit

Dominant language
Shell
Stars
3.2k
Forks
863
Avg merge
3h 15m
Merged PRs (30d)
2

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docker-install

All issues in docker/docker-install

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.