We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi all! I have docker-compose.yml
services: builder-mac: stdin_open: true restart: unless-stopped devices: - /dev/kvm image: sickcodes/docker-osx:naked ports: - 50922:10022 - 5999:5999 volumes: - /tmp/.X11-unix:/tmp/.X11-unix - /dev:/dev - ${PWD}/mac_hdd_ng.img:/image environment: - SIZE=200G - RAM=8 - DISPLAY=${DISPLAY:-:0.0} - EXTRA=-display none -vnc 0.0.0.0:99,password=on - DEVICE_MODEL=iMacPro1,1 - SERIAL=**************** - BOARD_SERIAL==**************** - UUID==**************** - MAC_ADDRESS==**************** - CPU=Haswell-noTSX - NETWORKING=vmxnet3 networks: main: ipv4_address: 192.168.100.10 networks: main: driver: bridge ipam: driver: default config: - subnet: 192.168.100.0/24 gateway: 192.168.100.1
Everything is work, but VNC password does not want to be saved. What i do:
docker compose attach builder-mac
(qemu) change vnc password
docker compose down
docker compose up -d
I repeat everything again and I connect successfully. I reboot the container - the password is unknown.
Please tell me how to fix this? How can I force it to save the VNC password? Thank you advanced!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi all!
I have docker-compose.yml
Everything is work, but VNC password does not want to be saved.
What i do:
docker compose attach builder-mac
(qemu) change vnc password
docker compose down
and thandocker compose up -d
I repeat everything again and I connect successfully. I reboot the container - the password is unknown.
Please tell me how to fix this? How can I force it to save the VNC password?
Thank you advanced!
The text was updated successfully, but these errors were encountered: