wago / docker-ipk Goto Github PK

This repo contains static linked binaries of docker ce packed in linux ipk format.

License: Apache License 2.0

pfc200 touchpanel edge-controller docker-ce linux-ipk-format arm32v7 docker

docker-ipk's Introduction

docker-ipk-preview

This repo contains static linked binaries of docker ce packed in linux ipk format. Check Release tags to get the newest version and needed FW.

How to install Docker CE on Wago devices.

Prerequisites for tutorial

Wago PFC Generation 2 (e.g. 750-8212, 750-8213..)
Wago Touch Panel 600 (e.g 0762-4104, 0762-4103..)
Edge Controller (e.g 0752-8303..)
CC100 PLC (e.g. 751-9301..)
ALL DEVICES: => with min. firmware 12 or higher installed in flash.

Notice: Only FW 17-18-19 is supported for older Versions.
Using actual Version fits since FW20 up to date.

for firmware download or update see: https://github.com/WAGO/pfc-firmware
Wago docker.ipk
PC with preinstalled SSH Client (e.g. https://www.putty.org/)
Web browser of your choice. (e.g. chrome)

Installation

Start Wago PFC.
Open WBM (Web Base Management) menu "Software Uploads".

Navigate to wago docker IPK. (e.g. docker_xx.xx.xx_armhf.ipk)
Then press "Install" button.
After finishing, you should see the success message.

Open menu "Networking -> Routing" and activate the IP Forwarding chekbox. (Don't forget to press the Submit button!)

Restart the PFC (e.g. menu "Administration -> Reboot")

PFC Login

Start SSH Client e.g. Putty

login as `root`
password `wago`

Check docker installation

docker info
docker ps # to see all running container (no container should run)
docker images # to see all preinstalled images

Enjoy the power of the whale!

Move docker "DATA-ROOT" to the SD card.

Due to the lack of memory on the "home" partition it is interesting to move the docker "data-root" to an SD card. This approach offers the following advantages:

positioning of more docker images on the PFC.
any images / containers can be pre-installed by replacing the SD card.
the physical portability of the images / containers increases.

Migration of docker "data-root"

Insert any SD card into the WAGO device (preferably WAGO SD card)
Open WBM (Web Base Management) menu "Mass Storage".

Select "Ext4" as file system type and assign a label for the SD partition (in our case "sd"). Then press the start button.
Stop running docker daemon.
```
     /etc/init.d/dockerd stop
```
Copy actual docker data root folder to sd card.
```
cp -r /home/docker /media/sd/
```

Edit daemon.json and change docker "data-root" entry.

vi /etc/docker/daemon.json or nano /etc/docker/daemon.json

Start docker daemon.
```
/etc/init.d/dockerd start
```

Check docker functionality.

docker info
docker ps # to see all running container 
docker images # to see all preinstalled images

DISCLAIMER:

THE OWNER MAKES NO WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE CONFIDENTIAL INFORMATION AND HEREBY EXPRESSLY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

docker-ipk's People

Contributors

Stargazers

Watchers

Forkers

sunnyhd helblingjuri rvacek99 cicai1631 jianfei209 dekoder igoralves1 cm0x4d shufanggui

docker-ipk's Issues

Not enough space on PFC200 G2

Hello,

We tried to install the Docker on PFC200 G2.

Here is the log:
Feb 26 03:09:36 PFC200V3-4F5C9C activate_download [2155] [Error]: [by shell command] (/usr/bin/opkg install /var/downloads/update-script/docker_20.10.5_armhf.ipk)
Feb 26 03:10:52 PFC200V3-4F5C9C activate_download [2232] [Error]: [internal error] (path /var/downloads/update-script/ is empty)

It is a fresh V16 installation.
It seems, that the space on the internal flash is not enough:

df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 126.7M 109.9M 10.0M 92% /
devtmpfs 245.9M 4.0K 245.9M 0% /dev
none 246.4M 16.0K 246.4M 0% /tmp
none 246.4M 0 246.4M 0% /media
none 4.0M 172.0K 3.8M 4% /var/log
none 246.4M 148.0K 246.2M 0% /var/run
none 246.4M 0 246.4M 0% /var/lock
none 246.4M 0 246.4M 0% /var/tmp
none 246.4M 0 246.4M 0% /sys/fs/cgroup
tmpfs 246.4M 116.0K 246.3M 0% /run
/dev/mmcblk0p1 16.0M 2.7M 13.2M 17% /boot/loader

Thank you for your help and regards,
Lukas Gaam

PermissionError: [Errno 1] Operation not permitted

Device TP600 (762-4102)
Firmware > 15
docker_20.10.5_armhf.ipk

Step to reproduce:
root@TP600-447D48:~docker run -it python:3.6 bash
root@6916a6997db1:/# python3
Fatal Python error: Py_Initialize: can't initialize time
PermissionError: [Errno 1] Operation not permitted

Current thread 0x76f39010 (most recent call first):
Aborted

The only workarounds i found was to launch with privileged, witch is not an optimal solution.

Proxy company for demon docker use

Hello,
How can I config for a proxy company use?
Best regard

Docker command not found

After docker instalation on PFC200 through web-based management I connected to plc via ssh.
I am getting docker not found.

Can't install docker

Hi !

Have some issues to install Docker !
I've already downloaded the IPK file, and uploaded on my PFC200, but after the Activation submit, there is a error (and that's ok as you said), but no docker command on my PFC.

I've checked to install it manually with the opkg command, but I guess my PFC can't install it cause my / partition is only 12M available.

So I checked mannually, but Docker ipk need need 115M !
But my / partition only got 82M as total size.. So how can we install it ?!

Then, i've tryied to install it on my SD card with the "-o" option on the opkg command.
But doesn't work, cause "Not selecting docker 18.09.0 due to incompatible architecture."

Dunno what to do now :/ !

Can you help me :( ?

Info :

WAGO 750-8202 PFC200 CS 2ETH RS
Firmware 03.00.35(12)

Docker daemon is not starting after reboot

Hi, I installed docker.ipk and I added an image and everythings is working. But after reboot, daemon is not starting automatically. Can anyone please help me? I searched the web and all are talking about systemctl and systemd, but there is no systemd on my device.

PFC100 Support?

The repository tags PFC100 but does not list it as a supported hardware, can you say anything about that?

Docker Update/Upgrade

Hello,
New release for docker, nice.
Nothing about upgrade in the Read-me, so I search on the docker doc and nothing about loosing data.
I thought it was as easy as upgrading a container just use the ipk and everything goes nice and smooth, damned i was so wrong....
After the upgrade where are my containers ?
Everything is gone and there is no warning nowhere about loosing anything ...
In the opkg i saw this:

_DOCKER_ETC="/etc/docker/"
DOCKER_DATA="/home/docker/"

# clean up files that are generated by dockerd
if [ -z "$DESTDIR" ]; then
	rm -rf "$DOCKER_ETC"

	umount -fl "$DOCKER_DATA"
	rm -rf "$DOCKER_DATA"
fi

exit 0_

Seriously ?
No warning about anything and the script delete all docker data.

Could you add libseccomp2 library to docker package?

I've expereincing problem with running latest HomeAssistant container without --privileged flag. Tho container output is:
Fatal Python error: init_interp_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted

This problem also discussed here: https://community.home-assistant.io/t/migration-to-2021-7-fails-fatal-python-error-init-interp-main-cant-initialize-time/320648/11
It's not HomeAssistant specific problem, it's more latest python/docker interaction problem.

Solution is to add libseccomp2 library that is used by modern docker engine.

Docker containers are not accessible from VPN

Ports exposed by docker are accessible on the local network, but not via VPN. I suspect rather firewall rules, as I can see docker modifying iptables for port forwarding.

DNS sometime not working on WAGO CC100 firmware version 23

I have the same configuration, on a WAGO CC100 with firmware version 21 it works, on a WAGO CC100 with firmware version 23, all DNS request made from inside the container timeout. Even when deactivating the firewall completely, it does not work.

To reproduce, install docker on WAGO CC100 with firmware revision 23 and do the following commands in a SSH connection:

root@CC100-XXXXXX:~ docker run -it --rm alpine
/ # nslookup www.wago.com
;; connection timed out; no servers could be reached
/ # exit
root@CC100-XXXXXX:~ nslookup www.wago.com
Server:		213.221.143.240
Address:	213.221.143.240:53

Non-authoritative answer:
Name:	www.wago.com
Address: 104.18.154.41
Name:	www.wago.com
Address: 104.18.155.41

So DNS works natively, but not inside Docker containers.