Skip to content

Scanopy: increase default CPU, RAM, and HDD to prevent OOM during Rust build#13130

Merged
CrazyWolf13 merged 2 commits intomainfrom
copilot/scanopy-fix-apt-configuration-error
Mar 20, 2026
Merged

Scanopy: increase default CPU, RAM, and HDD to prevent OOM during Rust build#13130
CrazyWolf13 merged 2 commits intomainfrom
copilot/scanopy-fix-apt-configuration-error

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 20, 2026

cargo build --release during Scanopy installation OOMs with the previous defaults (2 CPU / 3072 MB RAM / 6 GB HDD), causing a misleading APT configuration error.

Changes

  • ct/scanopy.sh: Bump container defaults to match build requirements:
Resource Before After
CPU 2 4
RAM 3072 MB 4096 MB
HDD 6 GB 8 GB

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.
Original prompt

This section details on the original issue you should resolve

<issue_title>[Scanopy] Error: APT: Configuration error (bad sources.list, malformed config)</issue_title>
<issue_description>Script: Scanopy

Reported by: @echocabinet

Guidelines

  • Read and understood guidelines: yes
  • Verbose mode used: yes

Issue occurs during: Initial Creation / Installation

Environment

  • Linux distribution: Debian
  • Proxmox version: 9.1
  • Default settings: No
  • Advanced settings: Yes
  • Exact command: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/scanopy.sh)"

Description

Initial install fails with Advanced Settings

Steps to reproduce

Run the script
Change CT number
Set static IP
Defaults for the rest

Error output

Error: APT: Configuration error (bad sources.list, malformed config)

Reading package lists...
[2026-03-20 09:24:06] [OK] Updated Container OS
[2026-03-20 09:24:06] [INFO] Installing Dependencies
[2026-03-20 09:24:16] [OK] Installed Dependencies
[2026-03-20 09:24:16] [INFO] Setup PostgreSQL 17
[2026-03-20 09:24:34] [OK] Setup PostgreSQL 17
[2026-03-20 09:24:34] [INFO] Setup Node.js 24
[2026-03-20 09:24:41] [OK] Setup Node.js 24
[2026-03-20 09:24:41] [INFO] Setting up PostgreSQL Database
[2026-03-20 09:24:41] [WARN] Granting SUPERUSER privilege (security risk!)
[2026-03-20 09:24:41] [OK] Set up PostgreSQL Database
[2026-03-20 09:24:41] [INFO] Fetching GitHub release: Scanopy (0.14.19)
[2026-03-20 09:24:42] [OK] Deployed: Scanopy (0.14.19)
[2026-03-20 09:24:42] [INFO] Setup Rust (1.90.0)
[2026-03-20 09:24:52] [OK] Setup Rust 1.90.0
[2026-03-20 09:24:52] [INFO] Building Scanopy Server (patience)
[2026-03-20 09:29:32] [ERROR] in line 32: exit code 101 (APT: Configuration error (bad sources.list, malformed confi
g)): while executing command cargo build --release --bin server --bin generate-fixtures
</issue_description>

<agent_instructions>add cpu to 4, ram to 4096, hdd to 8 in ct script</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@MickLesk Script working fine - i think here its an wrong output.

1.) OOM (need to increased to 4GB or its take many time) | 8 GB HDD should be default
2.) or network connection error because the build issue during dep generations

i fix the cpu / ram / hdd at first. Try again after this, if its not work run in verbose and deliver more information.

var_verbose=yes bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/scanopy.sh)" 
Image

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: MickLesk <47820557+MickLesk@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix APT configuration error in Scanopy installation fix(scanopy): increase default CPU, RAM, and HDD to prevent OOM during Rust build Mar 20, 2026
Copilot AI requested a review from MickLesk March 20, 2026 15:18
@MickLesk MickLesk changed the title fix(scanopy): increase default CPU, RAM, and HDD to prevent OOM during Rust build Scanopy: increase default CPU, RAM, and HDD to prevent OOM during Rust build Mar 20, 2026
@MickLesk MickLesk marked this pull request as ready for review March 20, 2026 15:21
@MickLesk MickLesk requested a review from a team as a code owner March 20, 2026 15:21
@github-actions github-actions bot added update script A change that updates a script bugfix labels Mar 20, 2026
@CrazyWolf13 CrazyWolf13 merged commit 2d46978 into main Mar 20, 2026
4 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bugfix update script A change that updates a script

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Scanopy] Error: APT: Configuration error (bad sources.list, malformed config)

4 participants