The UserSpace enables users to deploy and manage containers running on the rc_visard NG. Standalone containers and docker-compose stacks are supported.


Familiarity with Docker containers is required.

If available and enabled, the UserSpace can be accessed in the Web GUI in the menu under UserSpace. This page shows the running apps and containers with their current state and health, in case a health-check is available. Each container lists the published ports. If their protocol is http or https, these containers can be accessed directly in the Web GUI.


If the UserSpace is enabled for the first time, a user for the portainer UI needs to be created: In the Web GUI navigate to UserSpace and click on Manage UserSpace Apps. Then, register a user account for the administrator. It is required to complete this step within five minutes after booting the rc_visard NG.

Network access to UserSpace applications

To access containers via network, the container ports need to be published to host ports.

UserSpace information including running apps and their published ports can be queried via REST-API userspace endpoint or viewed in the Web GUI in the menu under UserSpace.

All ports that are published to the host are listed with their protocol (UDP or TCP). To explicitly specify a protocol (e.g. http or https) for app ports use container labels:

  • all exposed TCP ports use http
  •,5678: comma separated list with https ports


Docker containers managed in the UserSpace can use the public interfaces of the rc_visard NG. In particular, Docker containers can access synchronized image sets via gRPC and can call the REST-API interface. The rc_visard NG (the host) can be accessed under the Docker bridge IP (in default Docker bridge network


Some restrictions for containers apply:

  • Containers cannot be privileged.
  • No access to the host network (a Docker bridge network is used instead).
  • Only paths inside cloned git repositories with a docker-compose stack can be mounted, all other host paths cannot be mounted.
  • Host devices cannot be accessed. This includes e.g. USB and GPU devices.
  • Well known and internally used ports on the host cannot be bound. This includes ports below 1024, ports from 4200 to 4299 and the ports 2342, 2343, 2344, 2345, 3956, 4840, 5353, 6379, 7000, 7001, 7002, 7003, 9100, 9118, 9256, 9445, 9446, 11311, 22350, 22352, 50010, 50051, 50052, 50053 and 50054.