Troubleshooting¶

License Issues¶

If license validation fails:

Verify your SAS API credentials are correct (Account → SAS Credentials)
Check that your order number is valid
Ensure your SAS entitlement hasn't expired

Desktop Won't Start¶

Check Docker Desktop is running
Verify the SAS image is accessible (the extension pulls it automatically)
Check the operation status on the desktop card for error messages
Ensure you haven't exceeded your tier's desktop limit

First start is slow

The first start downloads a ~4 GB SAS image. Subsequent starts reuse the cached image.

Mount Issues¶

"Physical file is not accessible" in SAS¶

This usually means the directory is mounted but not added to the lockdown path allowlist. SAS lockdown is enabled by default and restricts which directories SAS programs can access.

Go to your desktop's Settings tab
Open the SAS Configuration section
Ensure Enable SAS Lockdown is on
Add your mount's target path to the lockdown paths (e.g. /data)
Save and restart the desktop

Tip

The extension auto-suggests lockdown paths from your configured mounts. Look for the "Suggest from mounts" chips below the path list.

Mount not working after container start¶

Verify the source directory exists and is accessible
Check Docker Desktop's file sharing settings — the source path must be in a shared directory
On macOS, ensure the path is under /Users, /tmp, /private, or another Docker-shared path
Review the mount status in the UI for validation errors

"Target path conflicts with reserved container path"¶

These paths are reserved and cannot be used as mount targets:

/opt/sas — SAS installation directory
/sasinside — License file directory
/sasuser — SAS user directory
/proc, /sys, /dev — Linux system directories

Choose a different target path like /data, /workspace, or /mnt/mydata.

"Permission denied" error¶

On macOS, check System Preferences → Security & Privacy → Files and Folders
On Linux, ensure the directory has appropriate read permissions for the Docker daemon
Try using Read-Only access mode if you only need to read files

"File not found" or "access denied" when starting a desktop with a local mount¶

Docker Desktop only shares certain host directories with containers by default. If your mount source path is outside these default shared paths, the container cannot access it.

Default shared paths:

Platform	Shared by default
macOS	`/Users`, `/Volumes`, `/private`, `/tmp`
Windows	`C:\Users`
Linux	`/home`, `/tmp`

If your source path is outside these locations:

Open Docker Desktop
Go to Settings → Resources → File sharing
Add the folder (or parent folder) that contains your mount source path
Click Apply & restart
Try starting the desktop again

Tip

The extension displays a warning during mount configuration if the path appears to be outside Docker Desktop's default file sharing scope.

Verify the UNC path format: //server/share (forward slashes)
Check that the credential profile has the correct username, password, and domain
Ensure the network share is accessible from your machine on port 445
Network shares require the Docker host to have network access to the file server

"Permission denied" when starting desktop with Azure Files mount¶

If you see an error like:

Error response from daemon: error while mounting volume: mount //storageaccount.file.core.windows.net/share: permission denied

This is almost always caused by incorrect credentials. Azure Files requires:

Username: The storage account name (e.g. mystorageaccount) — NOT your email address
Password: A storage account access key — NOT your personal password
Domain: Must be left blank

Common mistake

Do not enter your Windows login credentials, Entra ID (Azure AD) email/password, or AZUREAD\username format. Azure Files does not accept personal user credentials for SMB mounts from Docker containers. You must use the storage account name and access key.

To find your storage account key: Azure Portal → Storage Account → Security + networking → Access keys.

Azure Files mount works but per-user permissions are not enforced¶

This is expected behaviour. When mounting Azure Files with a storage account key, all access is performed as a single identity (the storage account). Per-user NTFS permissions cannot be enforced.

If your organisation requires per-user file security inside the SAS container, the storage must be hosted on a traditional Windows file server joined to Active Directory. See Network Share Mounts for details.

If clicking Sign In / Register does nothing (no browser window opens):

Check that Docker Desktop is up to date
Try restarting Docker Desktop
If the issue persists, contact Selerity support — this may indicate a server-side configuration issue

Note

The extension fetches authentication configuration from the Selerity gateway at sign-in time. If the gateway is temporarily unavailable or misconfigured, the button will appear to do nothing.

Check that your browser isn't blocking pop-ups from Docker Desktop
If you see a redirect_mismatch error, contact Selerity support — the callback URL may need updating for your installation method
Try a different browser as your system default

Session Limits¶

Tier	Session Limit
Starter (Free)	30 minutes
Personal	4 hours
Professional+	Unlimited

If your desktop stops unexpectedly, check your tier's session limit. Sign in or upgrade for longer sessions.

External Application Ports¶

SAS Enterprise Guide can't connect (IOM port)¶

Ensure the IOM toggle is enabled in Settings → Services and Ports
Verify the desktop is running
Check that SAS Integration Technologies Client for Windows is installed on your machine
Confirm the port number matches your connection definition in Enterprise Guide
If using a custom port, ensure it's not blocked by a firewall

VS Code SAS Extension can't connect (Compute Server port)¶

Ensure the Compute Server toggle is enabled in Settings → Services and Ports
Verify the desktop is running
Check your VS Code settings.json endpoint matches the configured port (default: http://localhost:8592)
Ensure the SAS Extension for Visual Studio Code is installed
Try restarting the VS Code SAS connection

Port conflict on start¶

If the desktop fails to start with a port conflict error:

Check that no two services on the same desktop use the same port
Check that no other desktop is running with the same port
Change the conflicting port to an unused value

Reporting Issues¶

Please report bugs via the Selerity website.

Include:

What you were doing when the issue occurred
What you expected vs. what happened
Screenshots if applicable
Docker Desktop version (docker version)
Operating system and architecture
Extension version (docker extension ls | grep selerity)