illacloud / illa Goto Github PK

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. Install Rust via Homebrew
2. Install illa cli tool via cargo: cargo install illa
3. Run command: illa deploy --self
4. See an error above

Expected behavior
ILLA Builder is deployed ok

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Macbook Pro, M1
• OS: Mac OS 12.4
• Browser: Chrome
• Version illa cli: 1.26

Additional context

• Rust 1.66
• Run Docker via Colima
• Docker version 20.10.16
• Colima version 0.5.2

Win11 21H2, Ubuntu 20.04 on WSL2. When running illa doctor, it stopped at the second step.

ravenz@DESKTOP-xxx:~$ illa doctor
🔍  Checking the prerequisites of self-host...
❌  No running docker found.
❗️  Please check the status of docker.

I have checked the status of docker. But it was running at that time.

ravenz@DESKTOP-xxx:~$ systemctl status docker
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-09-06 20:57:10 CST; 12h ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 13161 (dockerd)
      Tasks: 12
     Memory: 46.0M
     CGroup: /system.slice/docker.service
             └─13161 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

What should i do to fix it?

Describe the bug
Hey, I cloned this repo, installed dependencies, built the project and tried running the doctor subcommand. I got an information that No running docker found even though I have docker installed & running.

To Reproduce
Steps to reproduce the behavior:

1. Clone the repo
2. Inside the repo dir, run cargo run -- doctor
3. See an error

Expected behavior
I would expect the doctor subcommand to detect docker on my machine.

Screenshots

Desktop (please complete the following information):

• OS: MacOS Sonoma 14.0 (23A344)
• Docker version 24.0.6 installed via Docker Desktop

Additional context
Full docker info log:

 $ docker info
Client:
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-scout

Server:
 Containers: 28
  Running: 3
  Paused: 0
  Stopped: 25
 Images: 49
 Server Version: 24.0.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 6.784GiB
 Name: docker-desktop
 ID: b10b28d8-e296-4ac9-9514-17819097415a
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 68
  Goroutines: 89
  System Time: 2023-10-31T12:46:38.608889353Z
  EventsListeners: 11
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

Describe the bug
docker-compose ILLA_DEPLOY_MODE=SELF_HOST env vars do nothing.
the docs mention ILLA_DEPLOY_MODE=self-host and ILLA_DEPLOY_MODE='self-host' both of which seem to be incorrect unless the application does case and dash to underscore transformation.

To Reproduce
Steps to reproduce the behavior:

1. Go to link
2. follow instructions.
3. ui still asks you to enter email address to login.

Expected behavior
login with self_hosted mode

Desktop (please complete the following information):

• OS: linux
• Browser firefox
• Version 109

Additional context
Add any other context about the problem here.

Describe the bug
The contact us page on the website is no longer working and we cannot contact illacloud though any other means but this github

To Reproduce
Steps to reproduce the behavior:

1. Click on the "Contact Us" button on the website
2. Sign into Discord
3. Complete Captcha for joining the discord
4. Captcha fails "Link Invalid"

Expected behavior
Link Valid/a web form to contact illa cloud for business inquiries.

Additional context
Would like to discuss self hosted enterprise licensing for larger entities/entities requiring further regulatory compliance and there is no way to contact through the website to do that.

Request for changing the default mount address.

The default mount address (which is "/tmp" in Linux) will be erased after the system reboot.

Can we change it to stable dir like the current user's home dir or somewhere?

Describe the bug

PS C:\Users\Axel\Downloads\illa-x86_64-win> illa doctor
🔍  Checking the prerequisites of self-host...
✅  Docker version: 20.10.21
✨  Success! The minimum requirement for deploying ILLA has been satisfied. Self-Host your ILLA
PS C:\Users\Axel\Downloads\illa-x86_64-win> illa deploy --self --port=10000
🔨  Running a self-hosted installation...
✅  Downloaded in 4 seconds
❌  Start ILLA Builder error: expected value at line 1 column 1
PS C:\Users\Axel\Downloads\illa-x86_64-win>

To Reproduce
Steps to reproduce the behavior:

1. run illa deploy --self --port=10000
2. see error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: win10 22h2 19045.2486
• Browser chrome
• Version ???browser version? app version? os version?

Additional context
Add any other context about the problem here.

Describe the bug
在使用cli部署illa builder 后，注册账户及登录界面会显示网络异常。

Desktop (please complete the following information):

• OS: windows
• Browser: edge

Describe the bug
Start with illa deploy --self --port=10000 success but try to open 10000 failed

% curl http://localhost:10000
curl: (56) Recv failure: Connection reset by peer

Check the docker log for illa_builder find error

[envoy]  [2023-05-26 08:46:15.817][119][critical][main] [source/server/server.cc:113] error initializing configuration '/opt/illa/envoy/illa-unit-ingress.yaml': cannot bind '0.0.0.0:80': Permission denied
[envoy]  [2023-05-26 08:46:15.817][119][info][main] [source/server/server.cc:815] exiting
[envoy]  cannot bind '0.0.0.0:80': Permission denied

try to use local docker command line to start, also failed

docker run --rm -d --name illa_builder -e 'ILLA_SERVER_MODE=release' -e 'ILLA_DEPLOY_MODE=self-host' -e 'POSTGRES_PASSWORD=123456' -e 'ENVOY_UID=0' -e 'ENVOY_GID=0' -p 10000:80 --privileged docker.io/illasoft/illa-builder:latest

Docker images Id: b1734e2f3841

http://0.0.0.0:9999/api/v1/auth/signin 登录的时候看请求地址是这个，Mac下部署的

Current illa only supports deployment with Docker. Can support for Podman be provided?

Describe the bug
I am trying to build the standalone docker image version, because the existing tooling does not allow to remap WEBSOCKER_PORT or other ports:.

To Reproduce
Steps to reproduce the behavior:

1. clone https://github.com/illacloud/deploy-illa-manually
2. cd to docker,
3. run make build-docker-image
4. See an error

illa-builder:build-self: cache miss, executing 3bebdfaecb22dad3
illa-builder:build-self: 
illa-builder:build-self: > [email protected] build-self /opt/illa/illa-builder/apps/builder
illa-builder:build-self: > pnpm run ts-check && vite build --mode self
illa-builder:build-self: 
illa-builder:build-self: 
illa-builder:build-self: > [email protected] ts-check /opt/illa/illa-builder/apps/builder
illa-builder:build-self: > tsc --noEmit
illa-builder:build-self: 
illa-builder:build-self: vite v3.2.4 building for self...
illa-builder:build-self: transforming...
illa-builder:build-self: Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
illa-builder:build-self: ✓ 3704 modules transformed.
illa-builder:build-self: Terminated
illa-builder:build-self:  ELIFECYCLE  Command failed with exit code 143.
illa-builder:build-self: ERROR: command finished with error: command (/opt/illa/illa-builder/apps/builder) pnpm run build-self exited (1)

command (/opt/illa/illa-builder/apps/builder) pnpm run build-self exited (1)
 Tasks:    59 successful, 60 total
Cached:    0 cached, 60 total
  Time:    2m4.549s 

 ERROR  run failed: command  exited (1)
 ELIFECYCLE  Command failed with exit code 1.
The command '/bin/sh -c pnpm build-self' returned a non-zero code: 1

------------------------------------------------------------------------------------------------------

illasoft/illa-builder                                          latest                         74c8c548c35b   10 days ago      724MB

I tried updating npm, and purging some caches in the dockerfile

## clone frontend
WORKDIR /opt/illa/illa-builder
RUN cd /opt/illa/illa-builder
RUN pwd

RUN git clone https://github.com/illa-family/illa-builder.git /opt/illa/illa-builder/
RUN git submodule init; \
    git submodule update;

RUN npm cache clean --force
RUN npm install -g [email protected]
RUN npm cache clean --force
RUN npm install -g pnpm
RUN whereis pnpm
RUN whereis node

Expected behaviour

1. consistent usage of variables (this is high level issue I tried to fix myself)
2. npm actually build/install all the code.

Additional context

this should be a variable or something, there is some inconsistency, some are literal values, others are vars, some env vars are ignored by config script.

https://github.com/illacloud/deploy-illa-manually/blob/main/docker/config-init.sh#L30-L47

and here we set some variable but we do not use them:
https://github.com/illacloud/deploy-illa-manually/blob/main/docker/scripts/run-official-image.sh#L3-L38

we could do something like this:

# config here
PG_PASS=mysecretpassword
ILLA_HOME_DIR=/home/egidijus/things/deploy-illa-manually/docker/var/lib/illa
PG_VOLUMN=${ILLA_HOME_DIR}/database/postgresql
API_SERVER_ADDRESS=localhost
API_SERVER_PORT=29999
WEBSOCKET_SERVER_ADDRESS=localhost
WEBSOCKER_PORT=28000
WSS_ENABLED=false
ILLA_DEPLOY_MODE='self-host'


# init
mkdir -p ${ILLA_HOME_DIR}
mkdir -p ${PG_VOLUMN}
mkdir -p ${ILLA_HOME_DIR}
chmod 0777 ${PG_VOLUMN} # @todo: chmod for MacOS, the gid is "wheel", not "root". and we will fix this later.

# run
docker run -d \
    --name illa-builder \
    -e POSTGRES_PASSWORD=$PG_PASS \
    -e GIN_MODE=release \
    -e PGDATA=/var/lib/postgresql/data/pgdata \
    -e API_SERVER_ADDRESS=$API_SERVER_ADDRESS \
    -e API_SERVER_PORT=$API_SERVER_PORT \
    -e WEBSOCKET_SERVER_ADDRESS=$WEBSOCKET_SERVER_ADDRESS \
    -e WEBSOCKER_PORT=$WEBSOCKER_PORT \
    -e WSS_ENABLED=$WSS_ENABLED \
    -e ILLA_DEPLOY_MODE=$ILLA_DEPLOY_MODE \
    -v $PG_VOLUMN:/var/lib/postgresql/data \
    -p 25432:5432 \
    -p 7380:80 \
    -p $WEBSOCKER_PORT:$WEBSOCKER_PORT \
    -p $API_SERVER_PORT:$API_SERVER_PORT \
    illasoft/illa-builder:latest 

I'm working on WSL2. Podman is ready in my environment. I'm wondering if it's possible to support podman. As we know that Docker is not the only container tech, and Podman is very popular too.

Describe the bug
according to page : https://www.illacloud.com/zh-CN/docs/illa-cli

user can self-deploy illa using command:

illa deploy --self --port=10000 --server-addr=<SERVER_ADDRESS> --mount=<MOUNT_PATH>

To Reproduce
Steps to reproduce the behavior:

1. ./illa deploy --self --port=10000 --server-addr=192.168.89.129

root@ubuntu:/home/ubuntu/illa-x86_64-linux# ./illa deploy --self --port=10000 --server-addr=192.168.89.129
error: unexpected argument '--server-addr' found

Expected behavior

illa self-host deploy ok and host on addr 192.168.89.129

Desktop (please complete the following information):

• OS: ubuntu 22.04
• Version illa 1.2.9

Do not support non-root user to deploy or doctor.