[Bug]: all-in-one docker compose fails to build the management portal

Open Beginner friendly
#4,277 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker-compose
Domain
devops

Research direction

Start with distribution/all-in-one/docker-compose.yaml and check the management portal build context against the renamed portals/api-control-plane directory. Run docker compose up -d --build from distribution/all-in-one to confirm the failure is fixed and the all-in-one setup starts.

Written by the indexing model from the issue text.

Description

Aspect/API Aspect/Configuration Severity/Major Type/Bug
Please select the area the issue is related to

Platform API

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI), Aspect/Configuration (Config files, settings, env vars, defaults)

Description

distribution/all-in-one/docker-compose.yaml still builds the management portal from portals/management-portal, which was renamed to portals/api-control-plane. The all-in-one setup does not start.

Steps to Reproduce
  1. cd distribution/all-in-one
  2. docker compose up -d --build

Error:

unable to prepare context: path ".../portals/management-portal" not found
Severity Level of the Issue

Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)

Environment Details (with versions)

macOS, main (7e691fae2)

Dominant language
Go
Stars
85
Forks
137
Avg merge
1d 12h
Merged PRs (30d)
247

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wso2/api-platform

All issues in wso2/api-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.