Host your own instance and avoid such problems, or at least be in a position to fix them yourself.

I've been working on the docker part, taking my lumps but not bringing it up, as it isn't perl proper. I had a setback with following outdated instructions on the first attempt. I found a nice fresh how-to-install-docker-on-linux, from 31 January 2023, and have made considerable progress, but I can't quite get to where I successfully pull files. Fuller story in readmores:

All these commands went off without complaint:

apt update
apt-get remove docker docker-engine docker.io containerd runc

apt-get update
apt-get -y install ca-certificates curl gnupg lsb-release
mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --d
+earmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrin
+gs/docker.gpg] https://download.docker.com/linux/debian $(lsb_release
+ -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/n
+ull


apt-get update
apt-get install -y docker-ce docker-ce-cli containerd.io docker-compos
+e-plugin

systemctl start docker
systemctl enable docker

[download]

Output for root:

root@mypi:~# docker info
Client:
...

Server:
 Containers: 0
...
WARNING: No blkio throttle.write_iops_device support
root@mypi:~#

[download]

Looks all good. But then as pi, I failed:

root@mypi:~# exit
logout
$ which docker
/usr/bin/docker
$ docker info
Client:
...

Server:
ERROR: permission denied while trying to connect to the Docker daemon 
+socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdoc
+ker.sock/v1.24/info": dial unix /var/run/docker.sock: connect: permis
+sion denied
errors pretty printing info
$ whoami
pi
$

[download]

Then I thought, gosh, root can give pi permissions like this:

usermod -aG docker pi

[download]

, restart and see if I can pull some files:

$ docker info
...

Server:
 Containers: 0
  Running: 0
...
WARNING: No blkio throttle.write_iops_device support
$ whoami
pi
$ docker run -t -i -v $(pwd)/data:/code/data openelevation/open-elevat
+ion /code/create-tiles.sh  /code/data/SRTM_NE_250m.tif 10 10
Unable to find image 'openelevation/open-elevation:latest' locally
latest: Pulling from openelevation/open-elevation
345e3491a907: Pull complete 
...
4f4fb700ef54: Pull complete 
Digest: sha256:82fb21612e86ba847c1f30b6c9a2f457a26a929841a5754282ee2c9
+fea018639
Status: Downloaded newer image for openelevation/open-elevation:latest
WARNING: The requested image's platform (linux/amd64) does not match t
+he detected host platform (linux/arm/v7) and no specific platform was
+ requested
exec /code/create-tiles.sh: exec format error
$

[download]

I didn't understand this ultimate command, and I don't find any evidence of 

/code

[download]
on my machine.

Q1) Do I need to be worried about this mismatch?


WARNING: The requested image's platform (linux/amd64) does not match t
+he detected host platform (linux/arm/v7) and no specific platform was
+ requested

[download]

I know I've downloaded 1.2 gigs of data, but I don't know where: (?)

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  9.8G   18G  36% /
...
$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G   11G   18G  38% /
...
$

[download]

Fishing for tips from more experienced parties,

In reply to Re^5: approximating geological problems with highway data by Aldebaran
in thread approximating geological problems with highway data by Aldebaran

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.