Self-host LibreOffice (Remote Desktop) with Levelrail
A full LibreOffice desktop running in a container, reachable from any browser, for editing office documents.
- Memory1 GiB
- Archarm64
- Services1
How to self-host LibreOffice (Remote Desktop)
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/libreoffice:latest
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
LibreOffice (Remote Desktop) requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (lscr.io/linuxserver/libreoffice:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then LibreOffice (Remote Desktop). New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the LibreOffice (Remote Desktop) docs page.
Deploy LibreOffice (Remote Desktop) your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy LibreOffice (Remote Desktop) from the CLI
levelrail-cli templates deploy libreoffice --name my-libreoffice Deploy LibreOffice (Remote Desktop) with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/libreoffice/deploy LibreOffice (Remote Desktop) configuration
LibreOffice (Remote Desktop) services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| libreoffice | lscr.io/linuxserver/libreoffice:latest | 3000 | libreoffice_config -> /config |
LibreOffice (Remote Desktop) environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | libreoffice | Preset by the template |
| PUID | libreoffice | Preset by the template |
| TZ | libreoffice | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: libreoffice_config -> /config
LibreOffice (Remote Desktop) FAQ
How much memory does LibreOffice (Remote Desktop) need?
The catalog lists about 1 GiB of memory for LibreOffice (Remote Desktop).
Does LibreOffice (Remote Desktop) run on arm64?
For LibreOffice (Remote Desktop), an arm64 image is published; amd64 is image published.
Does LibreOffice (Remote Desktop) need configuration before it starts?
No. The template fills in its own defaults.
Which ports does LibreOffice (Remote Desktop) use?
LibreOffice (Remote Desktop) listens on port 3000 inside the stack.
Where does LibreOffice (Remote Desktop) keep its data?
In a named volume: libreoffice_config mounted at /config.
Can I deploy LibreOffice (Remote Desktop) on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for LibreOffice (Remote Desktop), so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/libreoffice:latest is what you deploy there.