-
Notifications
You must be signed in to change notification settings - Fork 17
Docker also runs on other architectures #22
Comments
The repo we get our docker-engine package from does not have an armhf binary/package. Maybe this will change with omv 3.x. |
@K0n24d When I started working on the plugin I believe only amd64 was a supported platform for Docker (not sure though). Since I only have an amd64 platform to work on myself, and I lack the time to set up/maintain etc. other platforms right now I will not add support for this myself. If you are able to submit PR's though that would enable armhf (or other platforms) I would happily merge them into the project code. |
Is there any news about this? I just changed the architecture line in debian/control file to all and rebuild the deb package. I installed on my OMV3 (raspberry pi flavour) and it works great. The only issue is with the "docker images repo" tab that is loading the images from http://openmediavault-plugin-developers.github.io/openmediavault-docker-repo/dockerlist.xml and those images are for amd64 architecture. Maybe change the code to download a dockerlist-${arch}.xml file will solve the problem. |
Since all of the other maintainers are very busy, I will look into this. The dockerlist should be easy to implement. I just don't know what to populate the armhf dockerlist with. |
I view that most of the images comes from linuxserver project. I think for armhf you can use the equivalents from lsioarmhf (https://hub.docker.com/u/lsioarmhf/) |
3.1.8 package in the docker testing repo. Didn't try on my RPi but it doesn't work on the xu4 image without modifying a few things. I didn't add any images to the dockerlist either. |
I installed, 3.1.8 version and it does not work for me too.
The only difference with the version I installed manually is openmediavault-omvextrasorg. I modified the Those are the diferences I made to make it working:
Do you think that the problem is with the openmediavault-omvextrasorg version difference? Or is in the new code to detect de architecture? |
I'm a little confused why you didn't use omv-extras 3.4.24 since it has been released? The architecture detection only determines which docker list to use. It doesn't affect anything else. Not sure why you can't connect to docker itself. |
I used 3.4.23 because it is the version I had installed. But since I tested the openmediavault-docker-gui 3.1.8, my OMV is inestable. I have a lot of errors like:
I'm going to reinstall a fresh OMV and test it again. |
The code changes in the latest docker and omv-extras plugins should not have made your system unstable. Lots of testing could have though. A fresh install should help. |
I installed a fresh OMV3 for my rpi, and updated all packages. Now I have the problem that docker-engine is not available. I don't know why, last time I installed it normally.
I followed the instructions from
Then I installed openmediavault-docker-gui normally and I have the docker service in OMV
But, if I go to the "docker images repo" tab, I view the images from amd64 arch. |
Did you enable both docker repos in omv-extras? When you install things from the command line, it makes it harder to fix the plugin. I forgot to plug my RPi in. I will do that later tonight. The docker images repo problem shouldn't be hard to fix. |
Yes, the problem is that the Now, I have this repo added to my apt:
Maybe the solution is add this repository?? |
Can't really check much until my RPi is on. What is the output of: apt-cache policy docker-engine |
|
Looks like the package exists on the repo that omv-extras adds. Not sure why you couldn't install it. I will figure that out later. |
Why did you limit this plugin to amd64 ?
Docker is running nicely on other architectures like armhf. You only need to pay attention to which images you use (but this is also true en amd64)
https://hub.docker.com/search/?q=armhf
The text was updated successfully, but these errors were encountered: