feat: build docker image with source code

[gy09535]

feat: build docker image with source code

[moonming]

is https://github.com/apache/apisix-docker good for you?

[gy09535]

I think it can not build code from local repos

is https://github.com/apache/apisix-docker good for you?

I think it can not build images from our private repository for secondary develop. If I change some code for our different logical, https://github.com/apache/apisix-docker can not work for me.

[juzhiyuan]

Do we have a final discussion result here?

[moonming]

@gy09535 Which part of the code did you modify? I'm not sure whether exposing the code directory will solve this problem?

[gy09535]

@gy09535 Which part of the code did you modify? I'm not sure whether exposing the code directory will solve this problem?

I want build the code with source code ,but I have change some code such as self define plugins. The https://github.com/apache/apisix-docker/blob/master/alpine/Dockerfile is build the code from github , but our code in our private repository . Now when the apache apisix has new release I merge it in our self repository and build a new image for our business. I think some company maybe has the same problem? So I think maybe we should add the Docker file in the source code and build with source code other then github code.

[moonming]

@gy09535 Got it.
The current dockerfile does not consider the situation of building from local source code. Welcome to PR to add, I transferred this issue to the apisix-docker project

[gy09535]

@gy09535 Got it.
The current dockerfile does not consider the situation of building from local source code. Welcome to PR to add, I transferred this issue to the apisix-docker project

I add the Dockerfile in apisix project, I think if we build it in source code ,we should add it in source code.

[gxthrj]

I think this feat is a better way, and we do not need to maintain multiple versions between different basic (os) images.

[gxthrj]

it is related to apache/apisix#2783

[github-actions]

This issue has been marked as stale due to 30 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.