LinuxSuRen / LinuxSuRen/api-testing

Running via Docker results in an error when accessing the web page.

Open
#871 0 comments 0 reactions 1 assignee View on GitHub

@yuluo-yx is already working on this.

Since Apr 3, 2026.

Dominant language
Go
Stars
369
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Image
Excepted

Normally, there should be no error message.

command
docker run --pull always -p 8080:8080 ghcr.io/linuxsuren/api-testing:master
logs
master: Pulling from linuxsuren/api-testing
Digest: sha256:e5dcdd3bd96e7aacf331f83c1d3626ce6f421412d5a731fa02aaa79ed09e46dd
Status: Image is up to date for ghcr.io/linuxsuren/api-testing:master
2026-04-03T11:01:19.969Z        INFO    loader  testing/loader_file.go:157      /var/data/api-testing/*.yaml        {"pattern": 0}
error occurred during getting stores, error: open /root/.config/atest/data/core/extension.yaml: no such file or directory
start to download linuxsuren/atest-ext-data-swagger
2026-04-03T11:01:19.969Z        INFO    server  cmd/server.go:301       gRPC server listening at   {"addr": "[::]:7070"}
2026-04-03T11:01:19.972Z        INFO    memory  mock/in_memory.go:110   start to run all the APIs from objects      {"count": 0}
2026-04-03T11:01:19.972Z        INFO    memory  mock/in_memory.go:117   start to run all the APIs from items        {"count": 0}
2026-04-03T11:01:19.972Z        INFO    memory  mock/in_memory.go:122   start webhook servers   {"count": 0}
2026-04-03T11:01:19.972Z        INFO    server  cmd/server.go:495       HTTP server started     {"addr": "[::]:8080"}
2026-04-03T11:01:19.972Z        INFO    server  cmd/server.go:496       gRPC server started     {"addr": "[::]:7070"}
2026-04-03T11:01:19.972Z        INFO    server  cmd/server.go:497       Server is running.
server is available at http://172.17.0.26:8080

Contributor guide

Open the 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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.