January-17th-2021, 09:40 PM
Ok now it is clear to me what you do.
To be honest I can't remember having tested the export function. I am pretty sure I have ... but long time ago ... and I am unsure if I have used the import function ever.
The hilschernetpi/netpi-openvpn container you are referencing is one of my latest developments. It uses indeed the Docker manifest function during container build times specifiying the correct architecture arm32v7 and also new arm64v8. If you visit the Docker site https://hub.docker.com/repository/docker...envpn/tags you see the supported architectures for the latest version.
The hilschernetpi/netpi-raspbian by the way also supports the manifest function. Visit the tag list as well https://hub.docker.com/r/hilschernetpi/n...pbian/tags and see the latest tags supports it already.
It is effort to change from the old build procedure to the new ones supporting manifest and including testing. This is why I had not find time to update all the other container you are referencing.
But back to your problem. You say you deploy the containers and they do their work ... for a while ... and then netPI starts to do weird things. But how does the export function help you? I think we should focus on debugging into details. I will write you a private message.
Thx
Armin
To be honest I can't remember having tested the export function. I am pretty sure I have ... but long time ago ... and I am unsure if I have used the import function ever.
The hilschernetpi/netpi-openvpn container you are referencing is one of my latest developments. It uses indeed the Docker manifest function during container build times specifiying the correct architecture arm32v7 and also new arm64v8. If you visit the Docker site https://hub.docker.com/repository/docker...envpn/tags you see the supported architectures for the latest version.
The hilschernetpi/netpi-raspbian by the way also supports the manifest function. Visit the tag list as well https://hub.docker.com/r/hilschernetpi/n...pbian/tags and see the latest tags supports it already.
It is effort to change from the old build procedure to the new ones supporting manifest and including testing. This is why I had not find time to update all the other container you are referencing.
But back to your problem. You say you deploy the containers and they do their work ... for a while ... and then netPI starts to do weird things. But how does the export function help you? I think we should focus on debugging into details. I will write you a private message.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
