Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] memory allocation failure on docker deploy #707

Closed
ex3me4me opened this issue Jun 7, 2022 · 2 comments
Closed

[BUG] memory allocation failure on docker deploy #707

ex3me4me opened this issue Jun 7, 2022 · 2 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@ex3me4me
Copy link

ex3me4me commented Jun 7, 2022

Environment

Self-Hosted (Docker)

Version

2.1.0

Describe the problem

Trying to deploy docker container, memory allocation failure error and container keep restarting over and over again.
deploying with "latest" tag, tried 2.0.9 - 2.0.6 same outcome.

VM Ubuntu 20.04.4 LTS
Ballooning 2GB ram
Docker version 20.10.16, build aa7e414

Temporary solution is to turn off ballooning and give the vm full 2GB to alocate, then container deploy with no problems.

Additional info

yarn run v1.22.15

$ npm-run-all --parallel build-watch start

$ node server

$ vue-cli-service build --watch --mode production

Checking config file against schema...

✔️ Config file is valid, no issues found

SSL Not Enabled: Public key not present

██████╗ █████╗ ███████╗██╗ ██╗██╗ ██╗

██╔══██╗██╔══██╗██╔════╝██║ ██║╚██╗ ██╔╝

██║ ██║███████║███████╗███████║ ╚████╔╝

██║ ██║██╔══██║╚════██║██╔══██║ ╚██╔╝

██████╔╝██║ ██║███████║██║ ██║ ██║

╚═════╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝ ╚═╝


Welcome to Dashy! 🚀

Your new dashboard is now up and running with Docker


Using Dashy V-2.1.0. Update Check Complete

✅ Dashy is Up-to-Date

  • Building for production...

WARN A new version of sass-loader is available. Please upgrade for best experience.

<--- Last few GCs --->

[66:0x7fe11678b350] 31234 ms: Scavenge 346.6 (358.3) -> 346.6 (359.3) MB, 4.8 / 0.0 ms (average mu = 0.283, current mu = 0.164) allocation failure

[66:0x7fe11678b350] 31314 ms: Scavenge 347.5 (359.3) -> 347.4 (364.1) MB, 79.4 / 0.0 ms (average mu = 0.283, current mu = 0.164) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

error Command failed with signal "SIGABRT".

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

ERROR: "build-watch" exited with 1.

error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Please tick the boxes

Fast, reliable, and secure dependency management.
@ex3me4me ex3me4me added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Jun 7, 2022
@liss-bot
Copy link
Collaborator

liss-bot commented Jun 7, 2022

Welcome to Dashy 👋
It's great to have you here, but unfortunately your ticket has been closed to prevent spam. Before reopening this issue, please ensure the following criteria are met.

Issues are sometimes closed when users:

  • Have only recently joined GitHub
  • Have not yet stared this repository
  • Have not previously interacted with the repo

Before you reopen this issue, please also ensure that:

  • You have checked that a similar issue does not already exist
  • You have checked the documentation for an existing solution
  • You have completed the relevant sections in the Issue template

Once you have verified the above standards are met, you may reopen this issue. Sorry for any inconvenience caused, I'm just a bot, and sometimes make mistakes 🤖

@liss-bot liss-bot closed this as completed Jun 7, 2022
@Lissy93
Copy link
Owner

Lissy93 commented Jun 7, 2022

Covered in the Troubleshooting guide.

Similar to #380, #350, #297, #349, #510 and #511.

If you can, please try and check the docs and past issues before opening a new ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
None yet
Development

No branches or pull requests

3 participants