Files
silverlinux-infra/mssql/README.md
T
Oclick021 a9a758d332 feat: Add slcompose service orchestrator with Infisical secret injection
- Add slcompose.sh: Central orchestrator for managing all Docker services
  * Boot all services at startup with automated Infisical secret injection
  * Commands: up, down, restart, logs, logs-tail, env, env-all
  * Colored environment variable output (blue names, green values)

- Add slcompose.service: Systemd service file for auto-boot on startup
  * Type=oneshot with RemainAfterExit=yes
  * Waits for Docker service before starting
  * Runs on multi-user.target

- Add orchestration.md: Comprehensive documentation
  * Architecture and installation guide
  * Usage examples for all commands
  * Secret injection flow and troubleshooting
  * Performance and security notes

- Update README.md and AI_CONTEXT.md
  * Document service orchestration architecture
  * Explain slcompose functionality and commands
  * Reference new orchestration documentation
2026-07-02 14:13:15 +03:30

117 lines
2.7 KiB
Markdown

# Microsoft SQL Server Express
## Overview
Microsoft SQL Server 2022 Express runs alongside PostgreSQL for Silver projects that require Microsoft SQL Server compatibility.
Status:
```text
Operational
```
Verified version:
```text
Microsoft SQL Server 2022 Express Edition (64-bit)
Linux
Version 16.0.4255.1
```
---
## Service Information
| Property | Value |
| --- | --- |
| Container | `mssql` |
| Image | `mcr.microsoft.com/mssql/server:2022-latest` |
| Edition | Express |
| Docker network | `internal` |
| Compose location | `/srv/docker/mssql/docker-compose.yml` |
| Data location | `/srv/docker/mssql/data` |
Port `1433` is not published by Docker or exposed through Nginx Proxy Manager. Applications connect privately over the `internal` Docker network using hostname `mssql`.
Server-side administration must use `docker exec` or another container attached to `internal`; there is no host-bound SQL port in the current configuration.
---
## Secrets
The SA password is provided by Infisical at runtime:
```text
MSSQL_SA_PASSWORD
```
Never commit the value to Git or place it directly in the Compose file.
---
## Deployment
The stack is deployed with Infisical injection instead of a local secrets file:
```bash
cd /srv/docker/mssql
infisical run --path=/ --recursive -- docker compose up -d
```
Secrets are injected into the environment before Docker Compose evaluates variables such as `${MSSQL_SA_PASSWORD}`.
Validate startup:
```bash
docker ps
docker logs mssql
```
Expected log message:
```text
SQL Server is now ready for client connections.
```
---
## Data Directory Permissions
The SQL Server container runs as UID and GID `10001`. For a new, empty deployment, initialize the bind-mounted directory with:
```bash
sudo mkdir -p /srv/docker/mssql/data
sudo chown -R 10001:10001 /srv/docker/mssql/data
sudo chmod -R 700 /srv/docker/mssql/data
```
Do not delete or recreate the directory after databases exist. Removing `/srv/docker/mssql/data` destroys the persisted SQL Server data.
---
## Troubleshooting
### Variable Is Not Set
If Compose reports that `MSSQL_SA_PASSWORD` is unset and defaults to a blank string, use the required `docker compose --env-file /srv/secrets/company.env up -d` command.
### System Directory Permission Denied
If `[/.system]` cannot be created, verify that `/srv/docker/mssql/data` is owned by `10001:10001` with mode `700`.
### Password Validation Failed
Confirm that the password meets SQL Server complexity requirements and that Compose resolved `MSSQL_SA_PASSWORD` from the secrets file.
---
## Related Documentation
* docs/server.md
* docs/services.md
* docs/security.md
* docs/secrets.md
* docs/backups.md
* dbgate/README.md
* postgres/README.md