We want to use the netPI as an IotEdge device (and replace the standard pi).
Since the netPI does not offer access to the linux console the Installation HowTo provided by Microsoft cannot be used.
How can the IotEdgeSecurityDeamon be installed on the netPI ?
Once the IotEdgeSecurityDeamon is installed, a config file (/etc/iotedge/config.yaml) needs to be edited. How do we gain access to that file?
Today I came across an offering from the web site Raspbian.org to download an .iso image of the latest Raspbian Desktop to run it under Windows or MAC.
In the latest fw version 1.1.4.0 there is a recurring issue that the session has expired. I have stopped and restarted the Docker Service. I have also tried setting the service to autostart and rebooting with no success. Please help.
I was wondering what the best way to obtain an unique identifier from within a docker container running on the netPI core 3. I'm using the netpi raspbian image and use the command
Code:
cat /proc/cpuinfo | grep Serial | cut -d ' ' -f 2
to read the serial, similar as I would on a regular Raspberry Ri. Is this id unique to the hardware or does it belong to the container? Is there any other unique identifier for the netPI core 3 available which is better than the one i obtain? Also, i notices that the id which you get by doing this contains the 6 last characters of the MAC-addr of the device and two additional characters which seem random. Are these random or is there a logical way to figure them out without using the command above?
Thank you!
Posted by: Armin@netPI - January-22nd-2019, 11:38 AM - Forum: News
- No Replies
A deep dive into Docker techniques shows that any container image relies on an base image in the layered file system.
Most of you might not have recognized that all our netPI example Docker images provided here are using base images from company resin.io.
Source of a base image are specified in the corresponding Dockerfile when a container is built. A typical entry looks like FROM resin/armh7f-debian:stretch.
October 2018 company resin.io announced to change their name to balena having an impact on the base image source location also.
Since January 2019 the old registry resin is no longer maintained. Instead the new registry balenalib can now be used as an immediate and compatible replacement.
So all you have to do is to change your previously set base image in your Dockerfile FROM resin/armh7f-debian:stretch to FROM balenalib/armh7f-debian:stretch and you are good.
I am using Rpi3 for building my custom image which I intend to run later on a Netpi. My requirement is to run Eclipse JDT on Net pi. So, I created a docker file with following commands in it.
------------------------------------------
FROM raspbian/stretch
RUN apt-get update
RUN apt-get install -y eclipse
RUN eclipse
---------------------------------------------
Before trying out with docker, I downloaded, Eclipse JDT on to the same Rpi by using the above commands in the same sequence and every time, I give "eclipse" on my terminal, the Eclipse IDE opens up. Since my RPi's OS is raspbian stretch which is what I am using in my custom image as well, I used same commands in same sequence in my Docker file as well. When I build the Docker file, the first 3 steps worked well but there popped an error while at the last step. Error message attached in the picture for your reference. I am very new to Docker so, I think I am missing some basics here and couldnot get what I intend to. Any suggestions from you will be of great help to me. Thanks in advance.
End of year 2018 the DockerHub community announced a refresh of the DockerHub web site. It was introduced as the "New DockerHub". For further details read on this Blog ...
...and indeed a few of you may have already recognized the DockerHub web site presenting itself in a new look. If not yet get your personal impression due to a quick visit of netPI's DockerHub registry..
Next to the changes on the frontend GUI the "New DockerHub" has improved also some backend functions such as the automated build process of Docker images based on GitHub or BitBucket projects which is a function that we were using since the beginning building the netPI example Docker images.
But now we have realized that since the roll out of the "New DockerHub" all existing netPI repositories are no more working in automated build mode. We are investigating this problem right now. The good thing is that all built and existing netPI image tags can be pulled from the repos still.
[Update]
I am happy to tell you that netPI Docker Hub registry operates again as it should. We turned all Classic Builds back into Automated Builds again.
I recently purchased a netPI RTE 3 through amazon. Initially the device would only boot partially, never actually starting the webserver.By browsing this forum i found the procedure to create a recovery USB drive.
I updated the Netpi and then was able to do complete boot.
Currently i can not log in to the portainer.io section. I activated docker but when i try to click on docker management and log in to portainer.io, it says my session is expired. Does anyone know how to overcome this issue?
I have been checking the 'netPI RE3' as profinet device/slave with netX inerface, CifX software and example provided, everything looks ok.
But i have a doubt is really there is not any chance to use this interface as profinet controller/master?? Best option recommended to work as profinet controller would be codesys and standard ethernet interface??
I'm using netPI RTE with the hilschernetpi/netpi-nodered-fieldbus container installed. Now I want to activate the LED 1 an 2 (GPIO12, GPIO 13).
I try a flow with output-node Raspberry rpi gpio. But it didn`t work, below the node the message N/A is shown. Sending an e-mail using the same trigger works.
Is it even possible to access the LED with Node-Red?
