Clarify documentation on how to Remote Access the TorizonCore GUI Using VNC or RDP

This is a document describing how to Remote Access the TorizonCore GUI Using VNC or RDP.
I have some doubts on what to do with docker-compoe.yml
The instructions say that I must add ENABLE_VNC=1 or ENABLE_RDP=1 but the video adds -ENABLE_VNC=1 (with the starting - character).
immagine
Looking to the command line for i.MX8M-Mini, it seems that this is expanded to --env ENABLE_VNC=1
But the “standard” docker-compose.yml for i.MX8M-Mini has

environment:
  ACCEPT_FSL_EULA: '1'

and it seems that this is expanded into -e ACCEPT_FSL_EULA=1

It’s not clear to me how to fill environment: section of docker-compose.yml so that it’s expanded in the expected way.
Is the following snippet correct for i.MX8M-Mini?

environment:
  ACCEPT_FSL_EULA: '1'
  -ENABLE_VNC=1

Hi @vix ,

From what I can see here is that there might be a typo in the video. I will forward that if that’s really the case. As from the docker documentation I can see this.

It seems like there has to be a space between “-” and “ENABLE_VNC=1”. I would expect that this has some effect on it.

environment:
  - ENABLE_VNC=1
  - ACCEPT_FSL_EULA=1

Can you try this and see if that changed anything?

Best Regards
Kevin

environment:
  - ENABLE_VNC=1

doesn’t work (or it seems so because I’m not able to access the Verdin in VNC).
Is there any additional configuration to be done?

My target is enabling VNC in the standard TorizonCore with Evaluation Container image.

Hello @vix ,
Can you try this in you docker-compose.yml file?
In the weston section:

 environment:
      ACCEPT_FSL_EULA: '1'
      ENABLE_VNC: '1'
      ENABLE_RDP: '1'
      DISPLAY: ':1'

Best regards,
Josep

I confirm that using

environment:
  ACCEPT_FSL_EULA: '1'
  ENABLE_VNC: '1'

with an indentation of two spaces (no -), works as expected.
Thanks