Test coverage
We validated Ollama 0.32.14 on a fresh Ubuntu 24.04.4 x86-64 VM and on an Apple-silicon Mac running macOS 26.4.1. The Linux archive SHA-256, macOS app archive SHA-256, Apple code signature, Gatekeeper assessment, model manifest, downloaded model blobs, and direct inference were checked. The standalone macOS tarball was rejected because strict app-signature verification did not apply; the signed Ollama.app archive is the supported path here.
Get more guides like this in your inbox
No spam. Unsubscribe anytime.
Ubuntu 24.04: download and verify
This is the same pinned install used by the passing Hermes baseline. It is for x86-64 Ubuntu only.
set -euo pipefail
sudo apt-get update
sudo apt-get install -y ca-certificates curl zstd
VERSION=0.32.14
ARCHIVE=ollama-linux-amd64.tar.zst
SHA256=c620917a71e146ab3a7f893084f066069c4c65d144ef8379a91c3cbe8b27de8f
curl --fail --show-error --location --retry 3 \
"https://github.com/ollama/ollama/releases/download/v${VERSION}/${ARCHIVE}" \
-o "/tmp/$ARCHIVE"
printf '%s %s\n' "$SHA256" "/tmp/$ARCHIVE" | sha256sum -c -
tar --zstd -tf "/tmp/$ARCHIVE" >/dev/null
sudo tar --zstd -xf "/tmp/$ARCHIVE" -C /usr
ollama --versionUbuntu 24.04: run it on loopback
For a chat-only installation, start Ollama as a service. For Hermes, keep the 64K environment value. Ollama's default endpoint is loopback; do not set OLLAMA_HOST to 0.0.0.0 in a beginner setup.
getent group ollama >/dev/null || sudo groupadd --system ollama
id ollama >/dev/null 2>&1 || sudo useradd --system --gid ollama \
--home-dir /usr/share/ollama --create-home --shell /usr/sbin/nologin ollama
sudo tee /etc/systemd/system/ollama.service >/dev/null <<'EOF'
[Unit]
Description=Ollama Service
After=network-online.target
[Service]
ExecStart=/usr/bin/ollama serve
User=ollama
Group=ollama
Restart=on-failure
Environment="OLLAMA_CONTEXT_LENGTH=64000"
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl daemon-reload
sudo systemctl enable --now ollama
curl --fail --silent http://127.0.0.1:11434/api/tags | jq .Apple silicon: verify the signed app
Use the official signed app archive. The sequence below extracts it under your own Applications directory, verifies Apple code signing and Gatekeeper, and avoids overwriting a system-wide installation. Quit any existing Ollama instance first so port 11434 is unambiguous.
set -euo pipefail
VERSION=0.32.14
ARCHIVE=Ollama-darwin.zip
SHA256=72f8545a4300ac597036e890fb5fa9a54b8ed5ec3032254d184ba9d9d59d2d51
DEST="$HOME/Applications/Ollama-$VERSION"
test "$(uname -m)" = arm64
mkdir -p "$DEST"
curl --fail --show-error --location --retry 3 \
"https://github.com/ollama/ollama/releases/download/v${VERSION}/${ARCHIVE}" \
-o "/tmp/$ARCHIVE"
ACTUAL=$(shasum -a 256 "/tmp/$ARCHIVE" | awk '{print $1}')
test "$ACTUAL" = "$SHA256"
ditto -x -k "/tmp/$ARCHIVE" "$DEST"
APP="$DEST/Ollama.app"
codesign --verify --deep --strict --verbose=4 "$APP"
spctl --assess --type execute --verbose=4 "$APP"
"$APP/Contents/Resources/ollama" --versionApple silicon: start the verified binary
This terminal-run method is what the isolated test exercised. Leave the terminal open, or later move the signed app into /Applications and launch it normally.
APP="$HOME/Applications/Ollama-0.32.14/Ollama.app"
OLLAMA_CONTEXT_LENGTH=64000 "$APP/Contents/Resources/ollama" serve
# In a second terminal:
curl --fail --silent http://127.0.0.1:11434/api/tagsChoose the first model
For the maintained Hermes baseline, use qwen3.5:9b. It passed on the 16 GiB Ubuntu CPU VM. Qwen 3.8 27B MLX needs about 18.17 GB just for model objects and is reserved for 32/36 GB-or-larger Macs; direct inference passed on 36 GB, but the full Hermes 64K profile timed out and remains experimental.
ollama pull qwen3.5:9b
ollama show qwen3.5:9b
ollama run qwen3.5:9b 'Reply with exactly OLLAMA_READY'
ollama psAcceptance checklist
The install is complete only when ollama --version reports 0.32.14, the local tags endpoint responds, a model returns the requested marker, and ollama ps shows the intended context after the model is loaded. If the machine is for Hermes, the context must be at least 64,000. Recheck the official release page and this guide's verification date before upgrading.