Skip to content
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

[🐛 Bug ]: Cannot start on Synology NAS #466

Open
mbrownnycnyc opened this issue Nov 26, 2024 · 2 comments
Open

[🐛 Bug ]: Cannot start on Synology NAS #466

mbrownnycnyc opened this issue Nov 26, 2024 · 2 comments
Labels

Comments

@mbrownnycnyc
Copy link

Operating System

DSM 7.2.1

Docker Image

budtmo/docker-android:emulator_13.0

Expected behaviour

docker container enters a running state.

Actual behaviour

It's not clear to me if docker-android will function on DSM v7.

I assume there's a kvm dependency for the container; is this correct?

Has anyone had success running any of the images on DSM v7?

ash-4.4# docker compose -f /volume1/docker/docker-compose-yml/android.yml up -d
[+] Running 27/1
 ✔ android 26 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                             328.0s
WARN[0328] Found orphan containers ([plex picard sonarr radarr jellyfin duckdns lidarr bazarr qbittorrent sabnzbd overseerr prowlarr]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 0/1
 ⠸ Container android_emulator  Starting                                                                                                                7.4s
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/home/androidusr/docker-android/mixins/scripts/run.sh": stat /home/androidusr/docker-android/mixins/scripts/run.sh: permission denied: unknown

The docker compose file is as follows:

version: '3.8'
services:
  android:
    image: budtmo/docker-android:emulator_13.0
    container_name: android_emulator
    ports:
      - "5037:5037" # ADB server
      - "5554:5554" # Emulator console
      - "5555:5555" # ADB device
      - "6080:6080" # VNC
    environment:
      - EMULATOR_DEVICE="Samsung Galaxy S10" # Adjust device if necessary
      - WEB_VNC=true
      - APPIUM=false # Disable Appium if not needed
      - AUTO_RECORD=false
    volumes:
      - /volume1/docker/android/androidusr:/home/androidusr
    restart: unless-stopped
    networks:
      vlan10:
        ipv4_address: 192.168.10.90
    dns:
      - 192.168.1.1

networks:
    vlan10:
        external: true

Permissions on the directory are as follows:

ash-4.4# stat /volume1/docker/android/androidusr
  File: /volume1/docker/android/androidusr
  Size: 0               Blocks: 0          IO Block: 4096   directory
Device: 25h/37d Inode: 17918017    Links: 1
Access: (0700/drwx------)  Uid: ( 1026/theusername)   Gid: (  100/   users)
Access: 2024-11-24 22:07:38.729244263 -0500
Modify: 2024-11-24 11:49:59.021044852 -0500
Change: 2024-11-24 22:07:35.099226282 -0500
 Birth: -

Any assistance is appreciated.

Logs

No response

@Fone-1
Copy link

Fone-1 commented Dec 9, 2024

remove volumes then you can start the compose project,i encountering the same issue

@W24663209
Copy link

version: '3'
services:
android:
image: budtmo/docker-android:emulator_11.0
container_name: android
environment:
- EMULATOR_DEVICE=Samsung Galaxy S10
- WEB_VNC=true
devices:
- /dev/kvm
restart: always
ports:
- "6080:6080"
- 5555:5555
You must have kvm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants