VSDS
A Vintage Story server. One command. Zero strange rituals.
Vintage Story Dockerized Server packages the server, its dependencies, and startup logic into versioned images. You choose the version, the port, and where to store the data. Docker takes care of the rest.
- Image
- xurxomf/vsds
- Compatibility
- Since 1.19
- Tags
- latest · stable · rc
- Persistent data
- /data
Docker
Deployment on Linux
Configure the container name, user, port, data folder, and version in a single command. Everything stays explicit, editable, and ready to fit your server.
The idea
The server is replaceable. Your world is not.
VSDS separates the application from persistent data. The container can be updated, removed, or rebuilt; worlds, players, configurations, mods, and logs remain in the folder you mounted as/data.
- 01
Docker Hub
Images prepared and tagged for each compatible server version.
- 02
VSDS Container
Server, dependencies, unprivileged user, and startup script in a reproducible environment.
- 03
Your /data
Worlds, configuration, players, mods and logs outside the container lifecycle.
ORIGIN
All the important things are in plain sight.
The persistent volume is a normal folder. You can edit `serversettings.json`, add mods in `Mods`, check `Logs`, or make your own copy without entering a black box.
Update without drama
New container, same data.
- 01
Stop and remove
Stop the previous container and remove it. The volume is not touched.
- 02
Change the tag
You choose a specific version or use `stable`, `rc` or `latest`.
- 03
Restart
You create the container with the same data path and the server continues where it was.
A detail that matters
It does not run as root. And that is good news.
In Linux, the container maps the internal user's UID and GID to those of the local user. This way, it can read and write to the volume without running with root privileges and without leaving a folder full of files that you later cannot touch.