-
-
Notifications
You must be signed in to change notification settings - Fork 506
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: Migrate from v1 (Python) to v2 (Go) #5034
Comments
pls use |
Many thanks for your report. Note that this is not the method we use in Go binaries should be self-contained, so not sure what is missing. The "not found" error can indeed happen when the binary is for a foreign architecture. Can you verify that you are indeed using an ARMv8 userland image and did not manually switch to the aarch64 kernel? dpkg --print-architecture And try to download the correct binary explicitly: curl -fL 'https://github.com/docker/compose/releases/download/v2.2.2/docker-compose-linux-aarch64' -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose Assure that there are not error messages, e.g. the |
@MichaIng |
The migration script does... moreless nothing. It downloads the Go binary like above and sets up When we do the migration, we shouldn't force it but inform users that a reinstall will apply it. I'd then simply uninstall the Python module and install the standalone binary 🙂. |
or we just apply v2 on new installations only and don't force a migration? |
I don't want to force it on a DietPi upgrade, but I also don't want to add/keep conditional Python 3 dependency and code in But this is something for DietPi v8.0, so still time to test and discuss about if and how 🙂. |
simply using the dietpi-software feature worked like a charm. sorry for the dumb question, but really appreciate the immediate responses, and for going easy on me :) |
Great. But thanks back for opening this issue, since I wasn't aware of Docker Compose v2 at all 😄. This should be more lightweight and cause less long-term issues with e.g. distro upgrades, as it does not depend on any external runtime, so I'm happy to implement it with DietPi v8.0 (since v7.9 is in beta already). |
Glad my extreme ignorance led to a useful discovery :) i'll keep asking stupid questions! |
- DietPi-Software | Docker Compose: We migrated from the Python-based v1 to v2, written in Go. Existing installs can be migrated with a manual "dietpi-software reinstall 134". Many thanks to @CommandLineN00b for making us aware of this major Docker Compose upgrade: #5034
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=8
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='applied'
G_LIVE_PATCH_STATUS[1]='applied'
G_LIVE_PATCH_STATUS[2]='applied'
Linux DietPi 5.10.63-v8+ #1488 SMP PREEMPT Thu Nov 18 16:16:16 GMT 2021 aarch64 GNU/Linux
Additional Information (if applicable)
Steps to reproduce
sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
docker-compose --version
Expected behaviour
Actual behaviour
Extra details
The text was updated successfully, but these errors were encountered: