-
-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | Docker Compose #3078
Comments
@Gill-Bates Simple binary install, talking care the dependencies manually: https://docs.docker.com/compose/install/ |
I had the same expectation that DietPi-Docker installed docker-compose with it and arrived here while researching the problem. It might be sensible to add it to the docker installation or at least add a prompt for "optional extras: ...".
|
@MichaIng |
I think since we pull docker-ce from official upstream sources as well, we should go with the up-to-date PyPI (pip) composer. There seems to be a pre-compiled wheel available for "any" architecture: https://pypi.org/project/docker-compose/#files |
I will do a comparison between RPi1,3,4 and VM Stretch/Buster this evening |
Below my test result Buster
Stretch
DietPi version
Software installed
Additional dependencies
On RPi 4
VM 1/2
Install command
Timing
On RPi1/3, most of the time is spend on |
Puhh, yes I remember pynacl being a major time consumer in other cases as well. The question is if many users will run a multi-container application on RPi 1/Zero anyway 🤔. I cannot imagine this being a good idea 😄. Strange that you didn't need libffi-dev + libssl-dev on RPi 4. Was it probably the 64-bit image so that arm64 vs armhf makes the difference here, i.e. there are pre-compiled pynacl wheels for arm64 but not for armhf? |
I was surprised as well that I don't need Looks like there is no pre-compiled |
This is not the only repository. non-64-bit RPis pull from piwheels.org as well, and very strange is that there are in fact PyNaCl wheels for ARMv7 and ARMv6 available for Python 3: https://www.piwheels.org/project/pynacl/ I do not remember where arm64/ARMv8 wheels are additionally pulled from. |
OK I was able to reduce runtime on my RPi3B+ from 28 minutes down to 30 seconds 😄 The trick is to specify RPi OS 64bit is not supported as it is still BETA https://blog.piwheels.org/raspberry-pi-os-64-bit-aarch64/ Logfile attached. Click to expand!
Question is, if we still need to install build dependencys |
Awesome. I wonder why it is not selected automatically as source, AFAIK it was, at least I remember certain bugs with the piwheels.org repo when Python 3 wheels were pulled by pip2 (resolved now). Looks like we should apply that source then for all ARMv6+ARMv7 boards, maybe there is a pip config for that. Who knows how much time was already waste to install dependencies and build wheels for modules which were pre-build on piwheels.org for a long time 😄.
Your log does not show a single source build but all were pre-built wheels, hence no build tools required 👍. |
https://www.piwheels.org/faq.html Using option |
Did one more test on my RPi B (without make dependency). Installation time is down to 2m35.960s from 160m24.768s bevor. Even faster than the RPi4B now 🤣 |
I'm still wondering why piwheels was already used as source in the past, like here: #3346 |
why not staying with option |
On the other hand we suggest
|
so we need to find a software not being available on |
You see the fallback already, |
Just installed OctoPrint on RPi without a single source build:
The same with I'd say it's safe to apply this on all ARMv6 + ARMv7 when installing Python 3 pip, then we can as well go through some software installs and likely are able to remove build dependencies in most cases. Would be awesome if there was some resource for arm64 wheels, but so far couldn't find any. |
Yes it could save a lot of time for our users doing this change. I guess arm64 will follow is soon as RPi OS 64bit will reach stable status. did you setup |
Yes, OctoPrint was just the first that came to my mind which pulls a lot of dependencies for testing. |
how did you config file looks like? |
Just your suggestion (=the one suggested by piwheels.org): #3078 (comment) |
ok I thought it could prevent still using |
As the settings name says, it's an "extra" index, no override 😃. |
bump would love to see this added! |
I'm running dietpi on rpi 3,
apt update
apt install docker-compose |
And what is the issue using |
sorry for being vauge
I think i needed to apt update inorder for it to work. |
looks like 64Bit as your kernel is There you have 2 options
|
thanks! @Joulinar Thanks for the support!For future people googling same issuehere's the steps i ended up using in the endLinkInstall Docker on Raspberry Pi: Installing Docker and Docker Compose on the Raspberry Pi in 5 Simple Steps - DEV# install python3 dependencies
sudo apt-get install -y libffi-dev libssl-dev
sudo apt-get install -y python3 python3-pip python3-setuptools
#check if python3 installed
python3 -V
# actuall install docker compose
pip3 install docker-compose -i https://www.piwheels.org/simple
docker-compose -v Dietpi version:
Hardware:
|
Basically Python could have been installed using |
so would this work?
|
no that's not how it is working it depends if you are running 32 or 64bit OS version as this would make a difference in packages needed 😉 |
two things:1) How do i get my hands on
|
Beta can be applied as follow. https://github.com/MichaIng/DietPi/blob/master/BRANCH_SYSTEM.md |
Dietpi offers docker inside dietpi-software catalog. But Docker-compose is missing. IMHO should be added.
The text was updated successfully, but these errors were encountered: