starred/godoxy
1
0
Fork 0
mirror of https://github.com/yusing/godoxy.git synced 2026-01-14 06:13:33 +01:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

go-proxy wont start after container creation #5

New Issue
Closed
opened 2025-12-29 09:21:33 +01:00 by adam · 3 comments
adam commented 2025-12-29 09:21:33 +01:00
Owner
Copy Link

Originally created by @earvingad on GitHub (Mar 28, 2024).

Hello,

  1. after building the docker container it won't start, you have to enter the container and manually start go-proxy
  2. it will fail to start due to missing schema folder/files.
  • In the Dockerfile it should be added the line COPY schema/ /app/schema

However, even after modifying the Dockerfile, go-proxy won't start automatically after starting the container.

Originally created by @earvingad on GitHub (Mar 28, 2024). Hello, 1. after building the docker container it won't start, you have to enter the container and manually start `go-proxy` 2. it will fail to start due to missing `schema` folder/files. - In the Dockerfile it should be added the line `COPY schema/ /app/schema` However, even after modifying the Dockerfile, `go-proxy` won't start automatically after starting the container.
adam closed this issue 2025-12-29 09:21:33 +01:00
adam commented 2025-12-29 09:21:34 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Mar 29, 2024):

  1. it will fail to start due to missing schema folder/files.
  • In the Dockerfile it should be added the line COPY schema/ /app/schema

yes you are right, will fix in the next commit

However, even after modifying the Dockerfile, go-proxy won't start automatically after starting the container.

after modifing the Dockerfile you have to rebuild it with docker compose up -d --build

@yusing commented on GitHub (Mar 29, 2024): > 2. it will fail to start due to missing `schema` folder/files. > * In the Dockerfile it should be added the line `COPY schema/ /app/schema` yes you are right, will fix in the next commit > However, even after modifying the Dockerfile, `go-proxy` won't start automatically after starting the container. after modifing the Dockerfile you have to rebuild it with `docker compose up -d --build`
adam commented 2025-12-29 09:21:34 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Mar 29, 2024):

Now should work, the Dockerfile is fixed

@yusing commented on GitHub (Mar 29, 2024): Now should work, the Dockerfile is fixed
adam commented 2025-12-29 09:21:35 +01:00
Author
Owner
Copy Link

@earvingad commented on GitHub (Mar 29, 2024):

Thank you! It is working now.

@earvingad commented on GitHub (Mar 29, 2024): Thank you! It is working now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
 wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?