Offline Installation (Linux)
When to Use Offline Installation
Choose offline installation when:
- Your server does not have internet access (air-gapped environment)
- Corporate security policies restrict internet downloads
- You need to install a specific version of Osprey
- Network connectivity is unreliable or very slow
- You want to maintain local copies of installation files
Prerequisites
Before starting offline installation, you'll need to prepare your system and download the required files.
System Preparation
Ensure Docker and Docker Compose are installed on your target system. See Pre-flight Checks for detailed installation instructions.
Download Osprey Installation Files
Contact Tycho Data team to get the latest version number and download the required files from a system with internet access.
Installation Files
Download the following files from Tycho Data:
osprey_1.0.122.tar- Main Osprey application imagepostgres.tar- PostgreSQL database imagetraefik.tar- Traefik reverse proxy imagedocker-compose.yml- Service configuration file- Any additional configuration files specific to your deployment
Installation Steps
1. Transfer Files to Server
Copy all installation files to your target Linux server using your organization's approved file transfer method:
# Example using scp (if network access is available)
scp osprey_1.0.122.tar postgres.tar traefik.tar docker-compose.yml user@target-server:/opt/osprey/
# Or use rsync
rsync -av osprey_1.0.122.tar postgres.tar traefik.tar docker-compose.yml user@target-server:/opt/osprey/
2. Load Docker Images
Navigate to the directory containing the tar files and load the Docker images:
# Change to installation directory
cd /opt/osprey
# Load Osprey image
docker load -i osprey_1.0.122.tar
# Load PostgreSQL image
docker load -i postgres.tar
# Load Traefik image
docker load -i traefik.tar
Verify the images are loaded:
docker images
You should see osprey, postgres, and traefik images listed.
3. Configure docker-compose
Place the provided docker-compose.yml file in your working directory. Review and modify any configuration settings as needed for your environment.
# Review the configuration
cat docker-compose.yml
4. Create / Update Database
Initialize the database with required schemas:
# Run database migrations
docker compose run --rm migrations
5. Configure SSL Certificate (Optional)
For HTTPS access, you can configure a self-signed certificate that Osprey will use. Work with the Tycho Data team to obtain or create a self-signed certificate for your environment.
Option 1: Use Certificate Provided by Tycho Data Team
Contact Tycho Data support to obtain pre-configured SSL certificates for your deployment.
Option 2: Create Self-Signed Certificate
If you need to create your own self-signed certificate:
Security Note: Self-signed certificates will show browser warnings. For production environments, consider obtaining certificates from a trusted Certificate Authority.
6. Start Services
Start all Osprey services:
# Start services in detached mode
docker compose up -d
# Monitor startup logs
docker compose logs -f
7. Verify Installation
Check that all services are running properly:
# Check container status
docker compose ps
# Check service health
docker compose logs
8. Test Web Access
Remote access test: From another machine, navigate to:
http://<server-ip>/
Set up account
From another machine, navigate to:
http://<server-ip>/start
Navigate the set up screens. An initial login will be created for you.
Post-Installation Configuration
Firewall Configuration
Configure firewall to allow external access:
Ubuntu
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw status
Service Management
Create systemd service for automatic startup:
# Create service file
sudo tee /etc/systemd/system/osprey.service > /dev/null <<EOF
[Unit]
Description=Osprey Application
Requires=docker.service
After=docker.service
[Service]
Type=oneshot
RemainAfterExit=yes
WorkingDirectory=/opt/osprey
ExecStart=/usr/local/bin/docker compose up -d
ExecStop=/usr/local/bin/docker compose down
TimeoutStartSec=0
[Install]
WantedBy=multi-user.target
EOF
# Enable service
sudo systemctl enable osprey.service
# Start service
sudo systemctl start osprey.service
Upgrades
To upgrade Osprey to a newer version in an offline environment:
1. Download Latest Osprey Image
Download the latest Osprey tar file from Tycho Data team:
Example (replace with latest version):
https://tychodataosprey.blob.core.windows.net/images/osprey_1.0.125.tar
2. Load New Docker Image
Load the new image on your target server:
# Load the new Osprey image
docker load -i osprey_1.0.125.tar
3. Update docker-compose Configuration
Open docker-compose.yml and update the Osprey image version to the new version:
services:
app:
image: tychodata/osprey:1.0.125 # Update to new version number
4. Stop Current Services
docker compose down
5. Start Updated Services
docker compose up -d
6. Verify Upgrade
Check that all containers are running with the new version:
# Check container status
docker compose ps
# Verify image versions
docker images | grep osprey
Note: Always backup your configuration and data before performing upgrades.
Next Steps
Once the services are running successfully, proceed to create your administrator account: