March-5th-2021, 08:34 AM
Hello Tad,
I think it is good to learn more about a Docker container and I want to teach you to find such kind of information yourself.
A Docker container has a build script file named "Dockerfile". In such a script file you find always the base image of a container that is loaded with the command "FROM ..." somewhere in the first lines of the script file.
On the web page of your link reference you sent https://hub.docker.com/r/hilschernetpi/netpi-raspbian you find link to the source code repository of the container always. It links to https://github.com/HilscherAutomation/netPI-raspbian. On that link you find the Dockerfile(s). Since netPI 3 is a 32bit container the relevant Dockerfile is "Dockerfile.arm32v7". If you open this file you see in the first statements "FROM balenalib/armv7hf-debian:buster-20191223". So the container uses as base image a debian:buster base image from December 23'th of year 2019.
Thx
Armin
I think it is good to learn more about a Docker container and I want to teach you to find such kind of information yourself.
A Docker container has a build script file named "Dockerfile". In such a script file you find always the base image of a container that is loaded with the command "FROM ..." somewhere in the first lines of the script file.
On the web page of your link reference you sent https://hub.docker.com/r/hilschernetpi/netpi-raspbian you find link to the source code repository of the container always. It links to https://github.com/HilscherAutomation/netPI-raspbian. On that link you find the Dockerfile(s). Since netPI 3 is a 32bit container the relevant Dockerfile is "Dockerfile.arm32v7". If you open this file you see in the first statements "FROM balenalib/armv7hf-debian:buster-20191223". So the container uses as base image a debian:buster base image from December 23'th of year 2019.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)