Jump to content


  • Posts

  • Joined

  • Last visited

  1. I think I can answer my own question, here. While attempting to pull an image for a LEMP stack (which was for armhf architecture) I got an error message something like “no [something or other] found for ARMv7” so it looks like Docker identified the HC2 board as ARMv7. I have a basic alpine image running but it’s available for all architectures. Hopefully someone will confirm or correct my hypothesis but I’m going to try to find and pull an image that’s specific to ARMv7 and see what happens.
  2. I’m running jammy and (I think) I’d like to upgrade to bullseye. But I can’t find a procedure for doing so. I’m guessing I can’t just dist-upgrade since jammy is Ubuntu and bullseye is Debian? I’ve googled for a procedure and searched this forum as well but I’m not finding a procedure. While searching this forum, I saw lots of topics where people had problems after upgrading to bullseye. Should I even do the upgrade? I don’t have much invested in the jammy install so far. Aside from running through armbian-config and getting all the settings the way I want them, the only things I’ve done are 1) installed Docker and 2) installed docker-compose. The latter was a major pain, though. I kept getting the “file not found” error. It took me hours to get it working and I’m still not exactly sure how I did it. Anyway, if my best course of action is to simply start over with the bullseye image, I can do that.
  3. Looking at various Docker images on Docker Hub, I see images for armv6, armv7, and armhf. Which are the right ones to use on an XU4/HC2?
  4. I'm trying to setup a server based on an Odroid HC2. I chose Armbian Buster but I'm having problems because arm64 isn't as well-supported as 32-bit. I'm thinking about starting over with Focal but I wanted to double-check first... Is Focal 32-bit? Does it still have/use armbian-config and softy? (I assume so, but just in case those are exclusive to Buster, I thought I'd ask.) Thanks for the guidance!
  5. In case anyone stumbles upon this and, like me, is trying to install docker-compose on Debian Buster-based Armbian (arm64 architecture) the answer, as it turns out, is quite simple... Install Docker using softy. (Softy does all the work - it's great!) I recommend testing the install with docker run hello-world Once that's done and successful, you can just run sudo apt install docker-compose and it just works. If you want to test it, paste this into docker-compose.yml: version: '3' services: web: image: nginx:latest ports: - "8080:80" links: - php php: image: php:7-fpm then run docker-compose up -d && docker ps
  6. I’m running Armbian 20.05.7 stable on an Odroid HC2 (XU4). I installed Docker Compose using the instrux found in the Linux section of the Docker install page. I’m logged in as root via SSH. I run the curl command (which I literally copied/pasted from the docs install page) curl -L "https://github.com/docker/compose/releases/download/1.26.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose then chmod +x /usr/local/bin/docker-compose and I check it with which docker-compose which returns: /usr/local/bin/docker-compose When I try to test the installation… docker-compose --version it returns: bash: /usr/bin/docker-compose: Permission denied Notice that it seems to want /usr/bin instead of /usr/local/bin, so (as suggested on the docs install page) I run ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose and I try to test the installation again. Now it returns: /usr/bin/docker-compose: line 1: Not: command not found I removed everything and tried the curl command (pointed at /usr/bin instead of /usr/local/bin) again, followed by the chmod command. Now which docker-compose returns /usr/bin/docker-compose So I try to test the installation again with docker-compose --version and I get the same thing: /usr/bin/docker-compose: line 1: Not: command not found What in the heck am I doing wrong? I tried posting this on the Docker forums but no one has responded so I'm wondering if it's more of an Armbian issue.
  • Create New...