Server packages the orchestration engine, web console, node agent, authentication service, proxy, catalog, and database into a Docker image for managing environments, hosts, stacks, services, containers, storage, and networking.
PastureStack is an independent community effort to preserve and modernize the
Rancher 1.6 ecosystem. It is not affiliated with Rancher Labs or SUSE.
This fork of rancher/rancher preserves
upstream history, authorship, licenses, and notices.
Server v1.6.537
packages Web Console 1.6.190 and Engine v0.183.350 for persistent
Stack/Service archive and restore. The official source/build, fresh startup/restart,
security/SBOM and anonymous artifact readback gates passed. See the
release note for the immutable producer and
image identities, archive behavior and bounded acceptance evidence.
Producer: f1df33f2a8b9e9265a9b8eeb9ad464786eb7f62e.
Manifest: sha256:81aafa0347910449ef528526f02e75a12acfce2f3987b803b92cb3b96fd0ac2d;
distinct OCI config: sha256:f49f36d2d6d2bd397c62330a0ff616aa8a3bbd5fce9cba10da45efabf9144363.
Documentation updates do not replace the producer or its immutable artifacts.
Personal API Keys remain available without an accessible environment. See the Host guide before enrolling a host.
Choose allow-by-default with deny exceptions, or deny-by-default with allow
exceptions, with optional expiry. Without exceptions these retain full or closed
access. Search for resource names; the editor and reviewed changes include a
resource-by-operation policy matrix, not an extra grant of authority. The maximum
access is the Key owner's current account/environment RBAC, including live
membership checks; a Key never grants an additional role. Existing legacy Keys
are not automatically narrowed on upgrade.
New Key secrets are shown once at creation and are not returned by later lists or
details. Per-Key audit separates authorization, the HTTP response and any later
job/stream completion. A successful WebSocket upgrade is recorded as a successful
HTTP 101 handshake, not as proof of the stream's later completion.
Environment-Key audit rechecks live Engine access in
Engine-verified project contexts; a caller-supplied project header is not a grant.
Delegated terminal/log access requires the verified Host API audit capability
and a compatible Linux Node Agent lifecycle. Open a Key's audit from its action
menu. See the API Key guide for policy and audit contracts.
Maintained CLI 0.6.18 propagates rejected requests as nonzero errors. Legacy 0.6.14 can silently exit zero; see client compatibility and check HTTP status explicitly for automation.
Public GHCR downloads do not require a registry login. Keep all three named volumes.
The examples below use the published numeric v1.6.537 tag.
docker run -d --name pasturestack-server --restart unless-stopped -p 8080:8080 \
-v pasturestack-cattle:/var/lib/cattle \
-v pasturestack-mysql:/var/lib/mysql \
-v pasturestack-mysqllog:/var/log/mysql \
ghcr.io/pasturestack/server:v1.6.537For HTTPS termination at a reverse proxy, set the exact public origin:
services:
pasturestack-server:
image: ghcr.io/pasturestack/server:v1.6.537
restart: unless-stopped
ports:
- "8080:8080"
environment:
PROXY_PLATFORM_PUBLIC_ORIGIN: https://stack.example.com
volumes:
- pasturestack-cattle:/var/lib/cattle
- pasturestack-mysql:/var/lib/mysql
- pasturestack-mysqllog:/var/log/mysql
volumes:
pasturestack-cattle:
pasturestack-mysql:
pasturestack-mysqllog:PROXY_PLATFORM_PUBLIC_ORIGIN accepts only scheme://host[:port], without
credentials, path, query, or fragment. Configure HTTPS, authentication, backups,
and access policies before exposing the platform. Supported JVM and embedded
MariaDB environment variables are in performance settings.
Back up the database and volumes, test a restore, then follow the
upgrade guide. Preserve existing volume names,
environment variables, restart policy, AppArmor, and reverse-proxy configuration.
Do not replace existing volumes with new empty ones or run docker compose down -v.
Persisted image/download/catalog/Docker compatibility settings can outlive an image upgrade; review their effective values. The migration tool is read-only by default and requires explicit apply/rollback. Keep the previous image and backup: after a database migration, rollback may require restoring matching data, not merely selecting an older image tag.
After using API Key policy or expiry, do not downgrade directly to a policy-unaware Engine: an older version can treat a restricted or expired Key as full access. Follow the API Key rollback safety guide before any downgrade or database restore.
GitHub Releases contain
versioned assets, SHA-256 checksums, and release records. Built-in templates come
from pinned catalog-templates
source. Historical changes belong in release notes.
Server consumes pinned source commits and verified component artifacts. For local source/shell validation:
bash scripts/test
bash scripts/check-server-source-gates.shRuntime, database migration, registration, backup/restore, and upgrade validation use isolated hosts. Publication is a separate, manually dispatched workflow. See ORIGIN.md and SECURITY.md.
The component candidate build uses the same release Dockerfile and verification
gates. server/build-component-candidate.sh requires actual component commits
and SHA-256 values; it does not publish or deploy. Set
PASTURESTACK_COMPONENT_ARTIFACT_DIR to an isolated directory whose contents
exactly match the complete component_assets list in
server/build-api-explorer-patch-image.sh.
Every asset is verified against its SHA-256 value. Without this directory, the
same hashes verify the versioned HTTPS release assets.
The console packages thirteen locales, including Traditional Chinese for Taiwan.
Server bootstrap messages accept PASTURESTACK_LOCALE=en-US or zh-TW;
protocol fields and persisted identifiers are not translated.
The inherited project uses Apache License 2.0, with attribution in COPYRIGHT_DETAILS.md. Bundled components retain their own licenses and notices.