Giter Club home page Giter Club logo

etherealengine / etherealengine-control-center Goto Github PK

View Code? Open in Web Editor NEW
33.0 11.0 13.0 2.01 MB

One stop solution for all your Metaverse needs. A desktop app for managing Ethereal Engine cluster. ๐Ÿค– ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐Ÿ‘“

Home Page: https://etherealengine.org

License: Other

TypeScript 84.80% JavaScript 0.98% CSS 1.33% EJS 0.07% Shell 7.92% PowerShell 4.89%
electron nodejs xr augmented-reality kubernetes minikube react virtual-reality metaverse docker

etherealengine-control-center's Introduction

Ethereal Engine Control Center

Want to build the spatial web on your website? Looking for a place to start? Run a web metaverse cluster yourself on your own computer.

The Ethereal Engine Control Center is a self-contained Metaverse world in a box. Take what you need or launch the full stack. Ethereal Engine Control Center is a desktop app to manage a metaverse cluster.

We know it's been complicated to build with #EtherealEngine and we've made this tool to give the community easy access to the engine for development and creation. The full Kubernetes cluster can run on Windows and any Debian Linux distro with at least 16 GB of ram.

We would love to see your creations and invite you all to come build with us. We've got a long backlog and need your help to build the Open Metaverse. Come build with us!

XREngine-Control-Center.mp4

Getting Started

You can find complete getting started guide here.

Additionally, there are Control Center video tutorials which you can find here. Although some of them might be outdated.

Install Released

Download latest version of Ethereal Engine control center app from here.

  1. (Windows) Directly download the .exe file.
  2. (Linux) For AppImage: Once downloaded, right click and go to Properties. In Permissions tab check 'Allow executing file as program'. Then, double click on AppImage to launch the app.

Note: Currently the app is tested on Windows 11 and Ubuntu 20.04 & 22.04.

Troubleshooting

1. App not launching in Ubuntu 22.04

Install Fuse:

sudo apt-get install fuse libfuse2 -y

2. Windows permission to run ps1 scripts

On Windows, if you get following error in logs:

.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

You need to allow running unsigned powershell scripts on your machine. You follow below steps to do so:

  1. Open Powershell as administrator.
  2. Run following command to find out your current execution policy.
Get-ExecutionPolicy
  1. Run following command to set the execution policy to allow unsigned scripts.
Set-ExecutionPolicy -ExecutionPolicy Unrestricted

You can read more on powershell execution policy.

3. Snap & MicroK8s k8s commands showing 'incorrect number of tail fields' error in Windows WSL

On Windows, if you get error in logs like below:

system_key.go:129: cannot determine nfs usage in generateSystemKey: cannot parse mountinfo: incorrect number of tail fields, expected 3 but found 4
cmd_run.go:1046: WARNING: cannot create user data directory: cannot determine SELinux status: failed to obtain SELinux mount path: incorrect number of tail fields, expected 3 but found 4

This is due to Docker Desktop default installation location issue. You can read more on Microk8s Issue #3911 & Docker Issue #13318.

This issue is mainly due to Docker Desktop being installed in default location. Here are the steps you can follow to fix this:

  1. Uninstall existing installation of Docker Desktop in Windows.
  2. Download latest version of Docker Desktop for Windows.
  3. Open Command Prompt (cmd).
  4. Change current working directory to downloaded Docker Desktop folder. i.e.
cd "C:\Users\%USERNAME%\Downloads"
  1. Run following command to install Docker Desktop in a folder other than default one.
"Docker Desktop Installer.exe" install --accept-license --installation-dir=C:\Docker

4. Git status unavailable on Windows

On Windows, if you are unable to see Git status after cluster configuration and getting following error in logs:

git configs - "fatal: detected dubious ownership in repository at <path to engine directory>\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory <path to engine directory>\n"

This is due to the app not having permissions to read the Git config file. To fix this, run Ethereal Engine Control Center as administrator.

5. Reporting an Issue

If you face an issue please report it to Issues or reach out to us on Discord. Also please share following log files:

  1. Non-UI logs found at following path:

    • on Linux: ~/.config/etherealengine-control-center/logs/main.log
    • on macOS: ~/Library/Logs/etherealengine-control-center/main.log
    • on Windows: %USERPROFILE%\AppData\Roaming\etherealengine-control-center\logs\main.log
  2. UI logs found using download button in app as shown in below image. LogsDownload

Install Development Release

Clone this repository:

git clone https://github.com/etherealengine/etherealengine-control-center.git ethereal-control-center

Go inside the folder:

cd ethereal-control-center

Install the dependencies:

npm install

Starting Development

Start the app in the dev environment:

npm run dev

Packaging for Production

To package apps for the local platform:

npm run package

Let's build it together

We believe that projects like this are extremely complex and difficult, and can only be built when large groups of people work together, out in the open. If you believe that your calling is to build a free, open network that everyone, everywhere can get value from, then you are welcome in our community, and we'll do our best to get you set up.

We are always hiring talented people who want to be leaders in what is to come. Inquire with anyone who seems like they know what's going on and they'll help you find who you need to talk to.

Your own sandbox in the Metaverse. Take what you need, or launch the full stack. Ethereal Engine Control Center is a desktop app for managing Ethereal Engine cluster.

Electron based Ethereal Engine Server Cluster Creator app

  • Ability to fully manage an on premises server.
  • Electron K8S Cluster Creator and Manager App
  • Easy setup and install deps (microk8s / minikube, docker etc) https://microk8s.io/
  • Wrap all K8S CLI into a GUI
  • Electron app with client for access to admin panel, supply link to open location in browser
  • Multiple electron apps with same k8s control plane
  • Benchmark tool - minimum specs of 4 CPU cores and 16-24GB of ram.

We Ethereal Engine believe that the Metaverse, Web AR, VR. XR should be easy.

etherealengine-control-center's People

Contributors

abhijay007 avatar ashish-aesthisia avatar citizendot avatar griffisaurus avatar hanzlamateen avatar hexafield avatar hurairahmateen avatar jerknose avatar moizadnan avatar mrhegemon avatar niralverma avatar zulqarnainhanif avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

etherealengine-control-center's Issues

[Initiative]: Create an Electron based EE Server Cluster Control Center App

PR NOTE @barankyle Update configurable drivers: https://minikube.sigs.k8s.io/docs/drivers/

Create an Electron based XR Engine Server Cluster Creator app

  • Ability to fully manage an on premises server.
  • Electron K8S Cluster Creator and Manager App

CORE

  • Easy setup and install deps
  • Wrap all K8S CLI into a GUI
  • Benchmark tool - detect min PC specs Probably has a min of 4 CPU cores and 16-24GB of ram.
  • Electron app with client for access to admin panel, supply link to open location in browser
  • Multiple electron apps with same k8s control plane

V1

V2

V3

V4

  • Dev mode
  • Add content packs (reality packs) to bundles.

V5

  • IPFS
  • BCIAB
  • P2P / SFU Chaining
  • Dynamic DNS to domain names
  • LifeScope

VS Code Extension?

https://code.visualstudio.com/api/get-started/your-first-extension

API ready count is empty

I created a machine over Google Cloud and after setting up the basics, I pressed the configure button and waited for it to make the necessary configuration, but for a few hours it gives this console error.

My Log:
log.txt

OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.15.0-1017-gcp
Ram: 32GB
Processor: Intel Xeon @ 8x 3.1GHz

[Epic] Full intergration test coverage

  • Ubuntu - Microk8s
  • Ubuntu - Minikube
  • Windows - Microk8s
  • Windows - Minikube (not supported currently)
  • MacOS - Microk8s
  • MacOS - Minikube (not supported currently)

WSL Login sometimes do not work in Windows

WSL Login not working in Windows when Window's username has spaces in it. This causes the Ethereal Engine's CC setup exe file to install control center in user folder which has space in the path and then it just breaks on wsl login step.

Ability to view pods in control center

Control center should have an ability to view pods. Right now we can only do it through admin tab and that too once the engine is installed and running.

Like this:
image

Save detailed logs

Control Center should have an option to download all log files which can be helpful to futher debug issues. This will allow to save all files as zip including:

  • Control Center UI logs
  • Control Center main process logs
  • Logs of all pods in cluster

Configure failed to start databases - host is already in use in another container

19:25:01: configure microk8s - Creating xrengine_test_db ...
19:25:01: configure microk8s - Creating xrengine_db ...
19:25:01: configure microk8s - Creating xrengine_minikube_db ...
19:25:01: configure microk8s - Creating elasticsearch ...
19:25:01: configure microk8s - Creating xrengine_redis ...
19:25:05: configure microk8s - Host is already in use by another container
19:25:06: configure microk8s - Creating elasticsearch ... error
19:25:06: configure microk8s -
ERROR: for elasticsearch Cannot start service elasticsearch: driver failed programming external connectivity on endpoint elasticsearch (9974aacedb8ff4d3e70ccf37d2f58149542f8ff2646eb819770e8087ad54cf92): Error starting userland proxy: listen tcp4 0.0.0.0:9300: bind: address already in use
Host is already in use by another container
19:25:06: configure microk8s - Creating xrengine_minikube_db ... error
19:25:06: configure microk8s -
ERROR: for xrengine_minikube_db Cannot start service minikubedb: driver failed programming external connectivity on endpoint xrengine_minikube_db (dabe024d1c7ac51bccfc3d005cfc89614fffcf0f40a38b0dd227b81c16fd097f): Error starting userland proxy: listen tcp4 0.0.0.0:3304: bind: address already in use
Host is already in use by another container
19:25:06: configure microk8s - Creating xrengine_db ... error
19:25:06: configure microk8s -
ERROR: for xrengine_db Cannot start service db: driver failed programming external connectivity on endpoint xrengine_db (0f3b2992a9e008ef6c64c47a1b4bc005eb1b053e8637c4d87f358d1c269542d2): Error starting userland proxy: listen tcp4 0.0.0.0:3306: bind: address already in use
Host is already in use by another container
19:25:06: configure microk8s - Creating xrengine_redis ... error
19:25:06: configure microk8s -
ERROR: for xrengine_redis Cannot start service redis: driver failed programming external connectivity on endpoint xrengine_redis (ae4cb4bfc96d7c259a0252de05fb8b88b2a3af22209a8982e56f145a49ab6429): Error starting userland proxy: listen tcp4 0.0.0.0:6379: bind: address already in use
Host is already in use by another container
19:25:06: configure microk8s - Creating xrengine_test_db ... error
19:25:06: configure microk8s -
ERROR: for xrengine_test_db Cannot start service testdb: driver failed programming external connectivity on endpoint xrengine_test_db (d997d5c15c3bb98534670bdaa982ac2624ecb90c058dddd85b304b14b1d76b0b): Error starting userland proxy: listen tcp4 0.0.0.0:3305: bind: address already in use

ERROR: for elasticsearch Cannot start service elasticsearch: driver failed programming external connectivity on endpoint elasticsearch (9974aacedb8ff4d3e70ccf37d2f58149542f8ff2646eb819770e8087ad54cf92): Error starting userland proxy: listen tcp4 0.0.0.0:9300: bind: address already in use

ERROR: for minikubedb Cannot start service minikubedb: driver failed programming external connectivity on endpoint xrengine_minikube_db (dabe024d1c7ac51bccfc3d005cfc89614fffcf0f40a38b0dd227b81c16fd097f): Error starting userland proxy: listen tcp4 0.0.0.0:3304: bind: address already in use

ERROR: for db Cannot start service db: driver failed programming external connectivity on endpoint xrengine_db (0f3b2992a9e008ef6c64c47a1b4bc005eb1b053e8637c4d87f358d1c269542d2): Error starting userland proxy: listen tcp4 0.0.0.0:3306: bind: address already in use

ERROR: for redis Cannot start service redis: driver failed programming external connectivity on endpoint xrengine_redis (ae4cb4bfc96d7c259a0252de05fb8b88b2a3af22209a8982e56f145a49ab6429): Error starting userland proxy: listen tcp4 0.0.0.0:6379: bind: address already in use

ERROR: for testdb Cannot start service testdb: driver failed programming external connectivity on endpoint xrengine_test_db (d997d5c15c3bb98534670bdaa982ac2624ecb90c058dddd85b304b14b1d76b0b): Error starting userland proxy: listen tcp4 0.0.0.0:3305: bind: address already in use
Encountered errors while bringing up the project.
19:25:06: configure microk8s - "Failed with error code 1."
19:25:06: configure cluster - "Failed with error code 1."

Error: INSTALLATION FAILED: execution error at (agones/templates/crds/gameserverset.yaml:16:21): Unknown feature gate "RollingUpdateOnReady"

Describe the bug
3:25:56 PM: configure minikube - [sudo] password for administrator:
3:25:56 PM: configure minikube - user logged in
3:25:56 PM: configure minikube - /tmp/.mount_XREngimUyaRp/resources/assets/scripts/configure-minikube.sh: line 46: node: command not found
3:25:56 PM: configure minikube - node is not installed
3:25:56 PM: configure minikube - /tmp/.mount_XREngimUyaRp/resources/assets/scripts/configure-minikube.sh: line 64: nvm: command not found
3:25:56 PM: configure minikube - nvm is not installed
3:25:56 PM: configure minikube - [sudo] password for administrator:
3:25:56 PM: configure minikube -
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

3:25:57 PM: configure minikube - Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
3:25:57 PM: configure minikube - Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
3:25:57 PM: configure minikube - Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
3:25:57 PM: configure minikube - Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
3:25:57 PM: configure minikube - Reading package lists...
3:25:58 PM: configure minikube -
3:25:58 PM: configure minikube - Building dependency tree...
3:25:58 PM: configure minikube -
Reading state information...
3:25:58 PM: configure minikube -
3:25:58 PM: configure minikube - 4 packages can be upgraded. Run 'apt list --upgradable' to see them.
3:25:58 PM: configure minikube -
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

3:25:58 PM: configure minikube - Reading package lists...
3:25:58 PM: configure minikube -
3:25:59 PM: configure minikube - Building dependency tree...
3:25:59 PM: configure minikube -
Reading state information...
3:25:59 PM: configure minikube -
3:25:59 PM: configure minikube - curl is already the newest version (7.81.0-1ubuntu1.6).
3:25:59 PM: configure minikube - 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
3:25:59 PM: configure minikube - % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
3:25:59 PM: configure minikube -
100 15916 100 15916 0 0 160k 0 --:--:-- --:--:-- --:--:-- 161k
3:25:59 PM: configure minikube - => nvm is already installed in /home/administrator/.nvm, trying to update using git

=>
3:26:00 PM: configure minikube - => Compressing and cleaning up git repository
3:26:00 PM: configure minikube -
3:26:00 PM: configure minikube - => nvm source string already in /home/administrator/.bashrc
3:26:00 PM: configure minikube - => bash_completion source string already in /home/administrator/.bashrc
3:26:00 PM: configure minikube - => Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion
3:26:00 PM: configure minikube - nvm version is 0.39.2
3:26:03 PM: configure minikube - v19.3.0 is already installed.
3:26:03 PM: configure minikube - Now using node v19.3.0 (npm v9.2.0)
3:26:03 PM: configure minikube - /home/administrator/.nvm/nvm.sh: line 3319: [: -ne: unary operator expected
/home/administrator/.nvm/nvm.sh: line 3323: [: -ne: unary operator expected
3:26:03 PM: configure minikube - /home/administrator/.nvm/nvm.sh: line 3335: [: -ne: unary operator expected
3:26:03 PM: configure minikube - node is installed
3:26:03 PM: configure minikube - node version is v19.3.0
3:26:04 PM: configure minikube - npm is installed
3:26:04 PM: configure minikube - npm version is 9.2.0
3:26:05 PM: configure minikube - python is installed
3:26:05 PM: configure minikube - python version is Python 3.10.6
3:26:05 PM: configure minikube - make is installed
3:26:05 PM: configure minikube - make version is GNU Make 4.3
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
3:26:05 PM: configure minikube - git is installed
3:26:05 PM: configure minikube - git version is git version 2.34.1
xrengine repo exists at /home/administrator/xrengine
3:26:05 PM: configure minikube - env file exists at /home/administrator/xrengine/.env.local
running npm install
3:26:14 PM: configure minikube -

[email protected] postinstall
patch-package

3:26:14 PM: configure minikube - patch-package 6.5.0
3:26:14 PM: configure minikube - Applying patches...
3:26:14 PM: configure minikube - [email protected]+oculus-multiview โœ”
3:26:14 PM: configure minikube -
Warning: patch-package detected a patch file version mismatch

Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:

Patch file created for

[email protected]+oculus-multiview

applied to

At path

node_modules/three

This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run

patch-package three

to update the version in the patch file name and make this warning go away.


patch-package finished with 1 warning(s).
3:26:14 PM: configure minikube -
up to date, audited 2624 packages in 9s
3:26:14 PM: configure minikube -
225 packages are looking for funding
run npm fund for details
3:26:14 PM: configure minikube -
38 vulnerabilities (20 moderate, 8 high, 10 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues possible (including breaking changes), run:
npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
3:26:14 PM: configure minikube - completed npm install
3:26:14 PM: configure minikube - docker is installed
3:26:14 PM: configure minikube - docker version is Docker version 20.10.12, build 20.10.12-0ubuntu4
3:26:15 PM: configure minikube - docker-compose is installed
3:26:16 PM: configure minikube - docker-compose version is docker-compose version 1.29.2, build 5becea4c
3:26:16 PM: configure minikube - UID PID PPID C STIME TTY TIME CMD
systemd+ 1236132 1235958 0 15:14 ? 00:00:00 mariadbd
3:26:16 PM: configure minikube - mysql is running
3:26:16 PM: configure minikube - virtualbox is installed
3:26:16 PM: configure minikube - vboxmanage version is 6.1.38_Ubuntur153438
3:26:16 PM: configure minikube - WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
3:26:16 PM: configure minikube - kubectl is installed
3:26:16 PM: configure minikube - WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
3:26:16 PM: configure minikube - kubectl version is Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:58:30Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
3:26:16 PM: configure minikube - helm is installed
3:26:16 PM: configure minikube - helm version is version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}
3:26:16 PM: configure minikube - minikube is installed
3:26:16 PM: configure minikube - minikube version is minikube version: v1.28.0
commit: 986b1ebd987211ed16f8cc10aed7d2c42fc8392f
3:26:17 PM: configure minikube - minikube status is minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
3:26:17 PM: configure minikube - host.minikube.internal entry exists
3:26:18 PM: configure minikube - *.etherealengine.com entries exists
3:26:18 PM: configure minikube - "agones" already exists with the same configuration, skipping
3:26:18 PM: configure minikube - "redis" already exists with the same configuration, skipping
3:26:18 PM: configure minikube - "xrengine" already exists with the same configuration, skipping
3:26:18 PM: configure minikube - Hang tight while we grab the latest from your chart repositories...
3:26:18 PM: configure minikube - ...Successfully got an update from the "xrengine" chart repository
3:26:18 PM: configure minikube - ...Successfully got an update from the "agones" chart repository
3:26:20 PM: configure minikube - ...Successfully got an update from the "redis" chart repository
Update Complete. โŽˆHappy Helming!โŽˆ
3:26:20 PM: configure minikube - helm repos added and updated
3:26:20 PM: configure minikube - Switched to context "minikube".
3:26:20 PM: configure minikube - Error: release: not found
3:26:20 PM: configure minikube - agones is not deployed
3:26:21 PM: configure minikube - Error: INSTALLATION FAILED: execution error at (agones/templates/crds/gameserverset.yaml:16:21): Unknown feature gate "RollingUpdateOnReady"
3:26:21 PM: configure minikube - "Failed with error code 1."

To Reproduce
Steps to reproduce the behavior:

  1. Click Configure
  2. Install
  3. See error

Expected behavior
Complete the installation

Desktop (please complete the following information):

  • OS: Ubuntu 22.04
  • Release : 0.0.9 Latest

Add a button in settings to clean the docker system for space issues

Currently if the space in docker is full the images failed to build. We can add a button in docker settings tab to clean the docker system for space issues.

Currently we need to manually run these commands:

eval $(minikube docker-env)
docker system prune
eval $(minikube docker-env -u)

Issue with MicroK8s status fetch

If I click on the refresh button, it seems to have lost the chowning/usermodding of microk8s with my user:

4:39:35 PM: MicroK8s - Insufficient permissions to access MicroK8s.
You can either try again with sudo or add the user kyle to the 'microk8s' group:

    sudo usermod -a -G microk8s kyle
    sudo chown -R kyle ~/.kube

Update Ubuntu prerequisite on windows to check for Windows Store version

The prerequisite on windows for Ubuntu should check for Windows Store version, right now it does not do that and configure wizard fails.

In assets\scripts\configure-microk8s-windows.ps1 file, around line 105 we have check to ensure You have WSL from the Windows Store.. We need this check to be part of Prerequisities as well.

MicroK8s hostname with Capital Caps

Test control center to include support for machines with capital caps in hostname or try with kubelet --hostname-override argument in microk8s.

Failed to install python package

19:48:35: configure microk8s - #10 60.11 debconf: unable to initialize frontend: Dialog
#10 60.11 debconf: (TERM is not set, so the dialog frontend is not usable.)
#10 60.11 debconf: falling back to frontend: Readline
#10 60.17 Setting up libpython3.7-minimal:amd64 (3.7.3-2+deb10u4) ...
#10 60.21 Setting up libexpat1:amd64 (2.2.6-2+deb10u6) ...
19:48:35: configure microk8s - #10 60.25 Setting up python3.7-minimal (3.7.3-2+deb10u4) ...
#10 60.36 Traceback (most recent call last):
#10 60.36   File "/usr/lib/python3.7/py_compile.py", line 212, in <module>
#10 60.36     sys.exit(main())
#10 60.36   File "/usr/lib/python3.7/py_compile.py", line 204, in main
19:48:35: configure microk8s - #10 60.36     compile(filename, doraise=True)
#10 60.36   File "/usr/lib/python3.7/py_compile.py", line 169, in compile
#10 60.36     importlib._bootstrap_external._write_atomic(cfile, bytecode, mode)
#10 60.36   File "<frozen importlib._bootstrap_external>", line 112, in _write_atomic
#10 60.36 PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.7/__pycache__/__future__.cpython-37.pyc.140470805858096'
#10 60.36 dpkg: error processing package python3.7-minimal (--configure):
#10 60.36  installed python3.7-minimal package post-installation script subprocess returned error exit status 1
#10 60.38 Errors were encountered while processing:
#10 60.38  python3.7-minimal
#10 60.42 E: Sub-process /usr/bin/dpkg returned an error code (1)
19:48:36: configure microk8s - #10 ERROR: executor failed running [/bin/sh -c apt-get -y install build-essential meson python3-testresources python3-venv python3-pip git]: exit code: 100
------
 > [ 4/13] RUN apt-get -y install build-essential meson python3-testresources python3-venv python3-pip git:
#10 60.36     compile(filename, doraise=True)
#10 60.36   File "/usr/lib/python3.7/py_compile.py", line 169, in compile
#10 60.36     importlib._bootstrap_external._write_atomic(cfile, bytecode, mode)
#10 60.36   File "<frozen importlib._bootstrap_external>", line 112, in _write_atomic
#10 60.36 PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.7/__pycache__/__future__.cpython-37.pyc.140470805858096'
#10 60.36 dpkg: error processing package python3.7-minimal (--configure):
#10 60.36  installed python3.7-minimal package post-installation script subprocess returned error exit status 1
#10 60.38 Errors were encountered while processing:
#10 60.38  python3.7-minimal
#10 60.42 E: Sub-process /usr/bin/dpkg returned an error code (1)
------
19:48:36: configure microk8s - ERROR: failed to solve: executor failed running [/bin/sh -c apt-get -y install build-essential meson python3-testresources python3-venv python3-pip git]: exit code: 100
19:48:36: configure microk8s - "Failed with error code 1."
19:48:36: configure cluster - "Failed with error code 1."

Cannot create Docker daemon.json directory non-existent

Configuring microk8s on Linux

19:09:14: configure microk8s - sh: 1: cannot create /etc/docker/daemon.json: Directory nonexistent
19:09:14: configure microk8s - "Failed with error code 2."
19:09:14: configure cluster - "Failed with error code 2."

Desktop (please complete the following information):

  • OS: Ubuntu 20.04.4 LTS

First Installation and Setup NPM Install Bug

Describe the bug
During the first installation of the Control Center on a fresh linux installation, the control center gets stuck on running npm install. I have tried manually installing Docker, Docker Compose, Virtual Box, kubectl, and Helm, but none have resulted in a fix

To Reproduce
Steps to reproduce the behavior:

  1. Set up a fresh install of linux ubuntu
  2. Install the XREngine Control Center
  3. Configure the settings with empty variables
  4. Stuck on configure minikube - running npm install for hours

Expected behavior
No idea, but it won't get past minikube setup

Screenshots
failure

Desktop:

  • OS: Ubuntu 22.04

Add prerequisite on windows for permission to run ps1 scripts.

Need to update prerequisites to check for script execution policy as well.

.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see 
about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.