daniel0076/megasync-vnc

By daniel0076

•Updated over 4 years ago

megasync with both VNC and web noVNC support

Image

395

Overview Tags

daniel0076/megasync-vnc repository overview

⁠Docker container for MEGASync on amd64 with VNC support

Make possible to run MEGA Sync⁠ with VNC

MEGASync version: The script will always fetch the latest version, reinstall image to upgrade
OS: Debian 11
Integrated CJK fonts support

The Docker baseimage comes from modified fork of jlesage/docker-baseimage-gui⁠. The GUI of the application is accessed through a modern web browser (no installation or configuration needed on the client side) or via any VNC client.

⁠Quick Start

This image has almost the same configuration as jleasage/docker-base-gui⁠ So only brief explaination is provided here, for detailed usage, please refer to jleasage's repo.

Launch the MEGASync docker container with the following command:

docker run -d \
    --name=MEGASync \
    -p 5800:5800 \
    -p 5900:5900 \
    -v $HOME/Downloads:/output:rw \
    daniel0076/megasync-vnc

Where:

$HOME/Downloads: This is the folder to sync with the MEGASync account

Browse to http://your-host-ip:5800 to access the MEGASync GUI, or you connect with a VNC client to vnc://your-host:5900.

⁠Usage

(Modified from jlesage's repo)

⁠Environment Variables

To customize some properties of the container, the following environment variables can be passed via the -e parameter (one for each variable). Value of this parameter has the format <VARIABLE_NAME>=<VALUE>.

Variable	Description	Default
`USER_ID`	ID of the user the application runs as. See User/Group IDs⁠ to better understand when this should be set.	`1000`
`GROUP_ID`	ID of the group the application runs as. See User/Group IDs⁠ to better understand when this should be set.	`1000`
`SUP_GROUP_IDS`	Comma-separated list of supplementary group IDs of the application.	(unset)
`UMASK`	Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl⁠	(unset)
`TZ`	[TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container.	`Etc/UTC`
`KEEP_APP_RUNNING`	When set to `1`, the application will be automatically restarted if it crashes or if a user quits it.	`0`
`APP_NICENESS`	Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. NOTE: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option `--cap-add=SYS_NICE`.	(unset)
`CLEAN_TMP_DIR`	When set to `1`, all files in the `/tmp` directory are deleted during the container startup.	`1`
`DISPLAY_WIDTH`	Width (in pixels) of the application's window.	`1280`
`DISPLAY_HEIGHT`	Height (in pixels) of the application's window.	`768`
`SECURE_CONNECTION`	When set to `1`, an encrypted connection is used to access the application's GUI (either via a web browser or VNC client). See the Security⁠ section for more details.	`0`
`VNC_PASSWORD`	Password needed to connect to the application's GUI. See the VNC Password⁠ section for more details.	(unset)
`X11VNC_EXTRA_OPTS`	Extra options to pass to the x11vnc server running in the Docker container. WARNING: For advanced users. Do not use unless you know what you are doing.	(unset)

⁠Data Volumes

The following table describes data volumes used by the container. The mappings are set via the -v parameter. Each mapping is specified with the following format: <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS].

Container path	Permissions	Description
`/output`	rw	This is the folder exposed to MEGASync .

⁠Ports

Here is the list of ports used by the container. They can be mapped to the host via the -p parameter (one per port mapping). Each mapping is defined in the following format: <HOST_PORT>:<CONTAINER_PORT>. The port number inside the container cannot be changed, but you are free to use any port on the host side.

Port	Mapping to host	Description
5800	Mandatory	Port used to access the application's GUI via the web interface.
5900	Optional	Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used.

Tag summary

Recent tags

Content type

Image

Digest

Size

233 MB

Last updated

over 4 years ago

docker pull daniel0076/megasync-vnc