asyncapi / .github

Location of all reusable community health files
29 stars 62 forks source link

Docker image fails to support Glee #275

Closed eelcofolkertsma closed 4 months ago

eelcofolkertsma commented 4 months ago

Describe the bug.

npm install fails in new glee project for missing python

I use asyncapi/cli image as poor man’s dev container in assumption that the image brings me all dependencies to work with asyncapi/cli features

my docker engine is hosted on raspberry pi 4

I am happy to work on solution, but also very much new to GitHub Actions and Building docker images.

Expected behavior

I can install and run-dev a new glee project in container based on asyncapi/cli image

Screenshots

image

How to Reproduce

Docker compose up below yaml for running container. My Docker engine runs on Raspberry Pi 4 current versions of OS and engine Fresh pull of asyncapi/cli image

version: '3'

services:
  studio:
    image: asyncapi/cli
    ports:
      - "8080:3210"
    volumes:
      - ${PWD}/asyncapi.yaml:/app/asyncapi.yaml
      - ${PWD}/output:/app 
    user: root
    networks:
      - default
    command: start studio

networks:
  default: {}
  1. attach to container for command prompt (I used Portainer)
  2. “Asyncapi new glee” to create new project
  3. “Cd project”
  4. “Npm install”

Install fails for lack of Python. The container is based on Alpine v3.18.3 Node version 16.20.2 Npm version 8.19.4 No python

🥦 Browser

Google Chrome

👀 Have you checked for similar open issues?

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

github-actions[bot] commented 4 months ago

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

eelcofolkertsma commented 4 months ago

Close as the issue is reported on wrong repo