List of pitfalls

in one place

Concise list of pitfalls described in this User guide.

Table of contents

1. List of pitfalls
   1. Using containers
      1. Skipping startup script
      2. WebGL disabled or unavailable
      3. Crashing applications
      4. Empty VNC password
   2. Keeping data
      1. Using bind mounts for $HOME
      2. Docker Desktop for Linux changes ownership
   3. Extending images
      1. Failing startup

Using containers

Skipping startup script

If you will skip the container startup script, then the container environment will not be fully configured.

Read more about this pitfall here.

WebGL disabled or unavailable

If you often visit web sites that require WebGL, then you may notice, that not all web browser images fully support WebGL by default.

It is not a bug, but a compromise decision favouring smaller image sizes over WebGL support.

Read more about it here.

Crashing applications

If applications are crashing, you may need to increase the shared memory (SHM) size.

Read more about it here.

Empty VNC password

Be aware, that some versions of some VNC viewers could have problems with empty VNC passwords (e.g. MobaXterm or TurboVNC).

Keeping data

Using bind mounts for $HOME

Learn here why you should avoid using bind mounts for the whole $HOME directory.

Docker Desktop for Linux changes ownership

If you’re on Linux and you have Docker Desktop for Linux installed, then read about this pitfall.

Extending images

Failing startup

If you’ve extended an accetto image and your container fails to start, then you may have the problem described here.

Previous Top Next