Operations¶
Review the known issues for this version, protect your state and diagnose problems without exposing credentials or customer data.
Known issues and maintenance¶
This guide covers package versions 0.1.12 and 0.1.13. Complete unfiltered scans for 0.1.13 on 17 October 2026 at 16:21 UTC retain 680 High and 104 Critical raw host matches on kernel identities, 72 High and zero Critical native-prefix matches on the retained linux-libc-dev SDK package identity, and zero High/Critical Python-runtime matches. These are scanner matches, not distinct proven exploitable vulnerabilities. Complete compiled-component coverage remains unverified. The full Software Sushi security gate has not passed.
The retained scans for 0.1.12 have the same High/Critical counts. Package 0.1.13 includes the customer launch, access and hands-on instructions under /opt/sushi/docs/README.md and /opt/sushi/docs/DEMO.md. Review your own returned text and table values against the source document.
At 16:31 UTC on 17 October 2026, the signed stable Ubuntu AWS kernel still lacks the required correction for CVE-2026-74446, which remains pending in the Ubuntu tracker. No finding has been suppressed or formally qualified as not affected. Successful automatic startup and document conversion do not certify a clean host or complete security coverage. Assess these limitations before deploying the image; updates require a newly verified image and a protected migration.
4. Protect state and plan upgrades¶
Application state is under /var/lib/docling; server configuration and private identity are under /etc/docling. Preserve those together with /home/ubuntu/.config/sushi/docling and any customer input/output directories. Treat backups containing credentials, documents, audio, metrics or repositories as private data. A single local EBS volume is not a redundant service or a backup.
For a consistent backup, finish active requests, stop the owning services below and take an encrypted EBS snapshot or protected file backup using your approved procedure. Preserve ownership and permissions. Start the same services afterwards and verify readback. Test restoration on a separate instance before replacing the original.
sudo systemctl stop sushi-docling-api.service
# Take and verify your protected backup while the services are stopped.
sudo systemctl start sushi-docling-api.service
A new Marketplace version does not update an existing instance. Launch the replacement separately, check state-format compatibility, restore only required customer state and verify your own read/write workflow before cutover. Keep a protected backup until the replacement is confirmed. Never erase a server identity as a routine upgrade step.
The generated self-signed TLS certificate expires after 365 days. Arrange an operator-reviewed certificate replacement before expiry, updating the client trust from the authenticated instance. Public DNS and certificate renewal automation are not included.
5. Diagnose a problem¶
sudo systemctl show sushi-docling-api.service -p ActiveState -p SubState -p NRestarts
sudo journalctl -u sushi-docling-api.service --no-pager -n 50
Inspect logs privately. Before sharing a support case, remove credentials, private hostnames and all customer content; include the Marketplace version, failing operation and a small invented reproduction. For connection errors, verify the correct Region/instance, Session Manager permissions, network endpoints and the active forwarding session. For input errors, check the package limits and request schema first. Do not install arbitrary replacement packages or delete customer state to force a retry.
Use the Software Sushi support contact and terms on the purchased Marketplace offer. Docling documentation explains the upstream project; it is not a support commitment from that project for this package.
Last updated October 17, 2026 · Suggest an improvement