sihyeonn opened a new pull request, #12754:
URL: https://github.com/apache/apisix/pull/12754

   ### Description
   
   This PR fixes a build failure when running `make build-on-debian-dev`.
   
   The debian-dev image build failed at:
   
   [2/2] STEP 9/21: COPY --chown=nobody:root ui/ /usr/local/apisix/ui/
   Error: building at STEP "COPY --chown=nobody:root ui/ 
/usr/local/apisix/ui/": checking on sources under 
"/var/tmp/libpod_builder971763380/build": copier: stat: "/ui": no such file or 
directorybecause the `ui` directory does not exist in the build context.
   
   To resolve this, the build script now ensures that an (empty) `ui` directory 
is created before building the debian-dev image, so the `COPY ui/ 
/usr/local/apisix/ui/` step always succeeds even when no UI assets are present.
   
   #### Which issue(s) this PR fixes:
   
   Fixes #
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [x] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to