cerc-io/stack-orchestrator
Archived
12
1
Fork 3
Code Issues 117 Pull Requests 25 Actions Packages Projects Releases 493 Wiki Activity

System requirements documentation #229

New Issue
Open
opened 2023-03-23 19:38:25 +00:00 by dboreham · 5 comments
dboreham commented 2023-03-23 19:38:25 +00:00
Contributor
Copy Link
Copy Source

We should add some text to the readme on what size machine you need, and whether cloud hosted VMs are suitable.
Also add something more about installing/verifying the docker installation.

We should add some text to the readme on what size machine you need, and whether cloud hosted VMs are suitable. Also add something more about installing/verifying the docker installation.
zramsay commented 2023-03-27 16:26:56 +00:00
Member
Copy Link
Copy Source

FWIW, I haven't run into any (obvious) problems on DO using:
8 GB Memory / 4 Intel vCPUs / 160 GB Disk

Hm, the answer to this really depends on the type of user and the stack they're running.

FWIW, I haven't run into any (obvious) problems on DO using: `8 GB Memory / 4 Intel vCPUs / 160 GB Disk` Hm, the answer to this really depends on the type of user and the stack they're running.
dboreham commented 2023-03-27 16:32:12 +00:00
Author
Contributor
Copy Link
Copy Source

Well, this takes is into the grey area : 8G is kind of skimpy but probably ok for most things, but do all our users know how to spot the condition when their system is OOM (which might manifest as processes mysteriously exiting)?

Same thing with 160G disk -- sounds like plenty but Docker burns through disk every time you build an image. It ends up using 100's of G if you work on the same machine for months in my experience. So then we need to help some of our users understand why their disk is full and how to remove orphaned images.

Well, this takes is into the grey area : 8G is kind of skimpy but probably ok for most things, but do all our users know how to spot the condition when their system is OOM (which might manifest as processes mysteriously exiting)? Same thing with 160G disk -- sounds like plenty but Docker burns through disk every time you build an image. It ends up using 100's of G if you work on the same machine for months in my experience. So then we need to help some of our users understand why their disk is full and how to remove orphaned images.
zramsay commented 2023-03-27 22:29:36 +00:00
Member
Copy Link
Copy Source

speak of the devil... Error processing tar file(exit status 1): write /app/node_modules/typescript/lib/tsserverlibrary.js: no space left on device

solved with docker system prune

speak of the devil... `Error processing tar file(exit status 1): write /app/node_modules/typescript/lib/tsserverlibrary.js: no space left on device` solved with `docker system prune`
zramsay commented 2023-03-29 14:07:59 +00:00
Member
Copy Link
Copy Source

#146 covers explaining docker; renamed this issue

#146 covers explaining docker; renamed this issue
zramsay commented 2023-03-29 14:11:23 +00:00
Member
Copy Link
Copy Source

#245 is our main bottleneck

#245 is our main bottleneck
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
K8s
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 in progress
invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
Copied from Github
An issue or PR manually copied from GitHub.
 Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
AFDudley Alex ashwin cerccicd ericlewis i-norden (Ian Norden) prathamesh (Prathamesh Musale) rachmaninovquar rjk-laconic roysc (Roy Crihfield) srw zramsay
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#229