
eisengrind/altv-voice-server
Searching for the alt:V server image? Click here
A Docker image providing the alt:V voice server.
release, release-2.8, 2.8
rc, rc-3.0-rc2, 3.0-rc2
dev, dev-2.2-dev12, 2.2-dev12
shdocker run --rm -it eisengrind/altv-voice-server:release
To the a full list of the latest tags and release of this Docker image, see the image on Docker Hub.
Here is a list of all available environment variables this image uses. The image maps environment variables to the voice server config file.
| Variable | Default value | Description |
|---|---|---|
ALTV_VOICE_SERVER_HOST | 0.0.0.0 | The voice server host address on which the voice is reachable for the alt:V server. |
ALTV_VOICE_SERVER_PORT | 7798 | The voice server port on which the voice server is reachable for the alt:V server. |
ALTV_VOICE_SERVER_PLAYER_HOST | 0.0.0.0 | A (static) ip on which the voice server is reachable for clients connected to the alt:V server. |
ALTV_VOICE_SERVER_PLAYER_PORT | 7799 | The voice server port on which the voice server is reachable for clients connected to the alt:V server. |
ALTV_VOICE_SERVER_SECRET | 1234 | A secret that the alt:V server uses to authenticate against the voice server. |
To use the environment variable when starting this Docker image:
shdocker run --rm -it -e ALTV_VOICE_SERVER_SECRET=*** eisengrind/altv-voice-server:release
sets the voice server secret to ***. See the Docker documentation on environment variables.
For the $build and $branch variables you have to enter the regarding alt:V versioning values.
$build represents the build number of the voice server binary. E.g. $build=1181
$branch represents the branch where the voice server binary was released. E.g. $branch=release.
shdocker build . --build-arg BRANCH=$branch -t eisengrind/altv-voice-server:$build
We provide two different kinds of tags for the alt:V Docker images: specific and non-specific image tags.
In general, this means that specific tags represent a unique alt:V build version whereas a non-specific tag such as release... or dev... represents the latest build number of the regarding branch.
Thus, once an image with a non-specific tag is pulled, this image will not automatically get updated by Docker unless you remove and pull the image again from Docker Hub.
This is why we provide specific tags. Those kind of tags do explicitly not lead to a caching problem, because specific tags are not meant to be, once they are published, changed.
tl;dr Keep in mind that you should always specify a specific tag in a Dockerfile.
Since this images inherits from the debian:buster-slim image, we schedule nightly builds every 24 hours to reduce security invulnerabilities.
We highly recommend to update the altv-server image as frequent as possible.
Keep in mind that, because of the frequent updates, we overwrite the image tags release, dev, rc aswell as their build versions.
To use a specific image, we recommend using their Sha-256 digest hash as an image selector.
See the LICENSE-file for further information.






探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务