Open kayx23 opened 7 months ago
@jingzhao-self I remembered you said your fix worked so it might or might not related to your change. When you are available, could you please test with the new image 3.8.0-debian
to see if you could reproduce this issue? Thanks.
cc: @monkeyDluffy6017 @shreemaan-abhishek
This issue is caused by docker-entrypoint.sh https://github.com/apache/apisix-docker/blob/2ddd3045bcc3a6f54116bf7559fa5918892423d8/debian/docker-entrypoint.sh#L23C1-L45C6
When in standalone mode this script tries to create the config.yaml file or update it's keys. I'm not quite sure why this done as we are able to provide ourselves a valid config.yaml when working in standalone mode.
I suggest removing the file update part. This way if the provided file is invalid the deployment would simply fail, but if it is not provided the script would create it for us.
I've come up with a simple fix to bypass the issue.
When working with the Docker image I override the entrypoint with bash
and set the command as -c "/usr/bin/apisix init && exec /usr/local/openresty/bin/openresty -p /usr/local/apisix -g 'daemon off;'"
This will start the gateway and forgo the entrypoint config file initialization.
Thanks, will you be opening a PR?
Yeah, sure. I can try that.
I've opened the pull request (https://github.com/apache/apisix-docker/pull/547). Hope we can fix it.
apache/apisix:3.9.0出现同样问题,volume配置文件没有效果
yep, it's not fixed yet...
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 dev@apisix.apache.org list. Thank you for your contributions.
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 dev@apisix.apache.org list. Thank you for your contributions.
Issue is still relevant
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 dev@apisix.apache.org list. Thank you for your contributions.
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 dev@apisix.apache.org list. Thank you for your contributions.
Current State
With the new
3.8.0-debian
image, I was unable to access route defined in theapisix.yaml
:Note that:
config.yaml
. In other words, if I just mountapisix.yaml
with a route config, I could access the route successfully.3.5.0
(unable to test with3.6.0
and3.7.0
due to sed error), so something may have changed. See screenshot below:Therefore, this looks like an error related to mounting
config.yaml
.Logs