VNC Naked version does not respect GENERATE_SPECIFIC #453

New Issue

2025-12-29T06:20:12+01:00

adam commented

2025-12-29 06:20:12 +01:00

Originally created by @mike-lloyd03 on GitHub (Dec 22, 2022).

When building an image with https://github.com/sickcodes/Docker-OSX/blob/master/vnc-version/Dockerfile.nakedvnc, I am unable to get it to generate specific serials/UUIDs passed in via the environment.

version: "3"

services:
  main:
    restart: unless-stopped
    devices:
      - /dev/kvm
    volumes:
      - /opt/docker/macvm/mac_hdd_ng_auto.img:/image
    image: docker-osx:nakedvnc
    ports:
      - 50922:10022
      - 5998:5999
    environment:
      - GENERATE_SPECIFIC=true
      - WIDTH=1600
      - HEIGHT=900
      - RAM=6

In my .env I have:

DEVICE_MODEL="MacBookPro9,1"
SERIAL=*********
BOARD_SERIAL=*****************
UUID=********-****-****-****-************
MAC_ADDRESS=**:**:**:**:**:**

But when I boot the machine, it is using the default serials and UUIDs. I think the problem is because the Dockerfile has two CMD instructions and only the second one is being executed (per Docker docs).

How can this Dockerfile be reworked to allow GENERATE_SPECIFIC to be honored?

Originally created by @mike-lloyd03 on GitHub (Dec 22, 2022). When building an image with https://github.com/sickcodes/Docker-OSX/blob/master/vnc-version/Dockerfile.nakedvnc, I am unable to get it to generate specific serials/UUIDs passed in via the environment. ```yaml version: "3" services: main: restart: unless-stopped devices: - /dev/kvm volumes: - /opt/docker/macvm/mac_hdd_ng_auto.img:/image image: docker-osx:nakedvnc ports: - 50922:10022 - 5998:5999 environment: - GENERATE_SPECIFIC=true - WIDTH=1600 - HEIGHT=900 - RAM=6 ``` In my .env I have: ``` DEVICE_MODEL="MacBookPro9,1" SERIAL=********* BOARD_SERIAL=***************** UUID=********-****-****-****-************ MAC_ADDRESS=**:**:**:**:**:** ``` But when I boot the machine, it is using the default serials and UUIDs. I think the problem is because the `Dockerfile` has two CMD instructions and only the second one is being executed (per [Docker docs](https://docs.docker.com/engine/reference/builder/#cmd)). How can this Dockerfile be reworked to allow `GENERATE_SPECIFIC` to be honored?

adam commented

2025-12-29 06:20:12 +01:00

@sickcodes commented on GitHub (Jan 12, 2023):

Yeah someone else created that file. I'll bring it in line with the others

@sickcodes commented on GitHub (Jan 12, 2023): Yeah someone else created that file. I'll bring it in line with the others

adam commented

2025-12-29 06:20:12 +01:00

@chirmstream commented on GitHub (Sep 5, 2023):

Mike, where you able to get your serials to be passed through? I believe I am having the same issue as you. I'll take a stab at fixing the nakedvnc Dockerfile if its still broken.

@chirmstream commented on GitHub (Sep 5, 2023): Mike, where you able to get your serials to be passed through? I believe I am having the same issue as you. I'll take a stab at fixing the nakedvnc Dockerfile if its still broken.

adam commented

2025-12-29 06:20:12 +01:00

@chirmstream commented on GitHub (Sep 14, 2023):

I had no luck with changing the nakedvnc docker file. I built my own copy of docker-osx:latest with my personal serials hard coded in, then built the nakedvnc container with the base image set to my own.

@chirmstream commented on GitHub (Sep 14, 2023): I had no luck with changing the nakedvnc docker file. I built my own copy of docker-osx:latest with my personal serials hard coded in, then built the nakedvnc container with the base image set to my own.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#453