dsavell/grav!grav
Grav is a Fast, Simple, and Flexible file-based Web-platform. There is Zero installation required. Although Grav follows principles similar to other flat-file CMS platforms, it has a different design philosophy than most.
The underlying architecture of Grav is built using well established and best-in-class technologies. This is to ensure that Grav is simple to use and easy to extend. Some of these key technologies include:
We utilise the docker manifest for multi-platform awareness. More information is available from docker here.
Simply pulling dsavell/grav:admin should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ❌ | arm64v8-<version tag> |
| armhf | ❌ | arm32v7-<version tag> |
This image provides various versions that are available via tags.
| Tag | Available | Description |
|---|---|---|
| admin | ✅ | Stable Grav Core + Admin plugin releases |
| core | ✅ | Stabe Grav Core releases |
| admin-<date> | ✅ | Stable Grav Core + Admin plugin releases + date |
| core-<date> | ✅ | Stabe Grav Core releases + date |
| admin-<version tag> | ✅ | Pinned Grav Core + Admin plugin releases |
| core-<version tag> | ✅ | Pinned Grav Core releases |
| admin-<version tag>-<date> | ✅ | Pinned Grav Core + Admin plugin releases + date |
| core-<version tag>-<date> | ✅ | Pinned Grav Core releases + date |
WebUI can be found at http://<your-ip>
More information can be found on the official documentation here
Here are some example snippets to help you get started creating a container.
yaml--- version: '2.1' services: grav: image: dsavell/grav:<TAG> container_name: grav restart: unless-stopped environment: - DUID=1000 - DGID=1000 - TZ=Europe/London # optional - GRAV_MULTISITE=subdirectory # optional - ROBOTS_DISALLOW=false # optional - GRAV_PLUGINS=devtools,precache # optional volumes: - /data/containers/grav/backup:/var/www/grav/backup - /data/containers/grav/logs:/var/www/grav/log - /data/containers/grav/user:/var/www/grav/user ports: - 80:80
bashdocker create \ --name=grav \ --restart unless-stopped \ -e DUID=1000 \ -e DGID=1000 \ -p 80:80 \ -e TZ=Europe/London `# optional` \ -e GRAV_MULTISITE=subdirectory `# optional` \ -e ROBOTS_DISALLOW=false `# optional` \ -e GRAV_PLUGINS=devtools,precache `# optional` \ -v /data/containers/grav/backup:/var/www/grav/backup \ -v /data/containers/grav/logs:/var/www/grav/logs \ -v /data/containers/grav/user:/var/www/grav/user \ dsavell/grav:<TAG> docker start grav
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 80 | Http webUI |
-e DUID=1000 | for UserID - see below for explanation |
-e DGID=1000 | for GroupID - see below for explanation |
-e TZ-e GRAV_MULTISITE=subdirectory | Deploy a Grav multisite (subdirectory) installation. |
-e ROBOTS_DISALLOW=false | Replace default /robots.txt file with one discouraging indexers. |
-e TZ=Europe/London | Set your timezone |
-e GRAV_PLUGINS=devtools,precache | Install extra plugins automaticall (must be comma separated) |
-v /var/www/backup | Contains your location for Grav backups |
-v /var/www/logs | Contains your location for your Grav log files |
-v /var/www/user | Contains your Grav content |
When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
bash$ id username uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
[***]master branch to main branch.commitlint function to verify proper commit messages..editorconfig to ensure standards across IDE's..gitattributes to ensure standards across git CLI.subdomain as an option for GRAV_MULTISITENGINX_CLIENT_MAX_BODY_SIZE to specify the nginx config client_max_body_sizebin/grav/ scheduler -i to startup output.crontab -l to startup output.探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务