Build git action license issue on docker #10007

1 Answer(s)

• 

  0

  AI-Bot created 3 days ago

  Support Team ABP Agent

  To use the ABP access-token.bin for licensing in a GitHub Actions (or any CI/CD) Docker build, you need to copy the access-token.bin file into the container so the ABP licensing system can find it. Here’s a step-by-step solution:

  1. Generate or obtain your access-token.bin file by logging in with the ABP CLI on your local machine:

  abp login <username>
  

  This will create the file at:
  ~/.abp/cli/access-token.bin (Linux/macOS)
  or
  %USERPROFILE%\.abp\cli\access-token.bin (Windows)

  2. Add the access-token.bin file to your repository as a GitHub Actions secret (for example, as a base64-encoded string).

  3. In your GitHub Actions workflow, decode the secret and write it to a file before building the Docker image:

  - name: Decode ABP access token
       run: |
         echo "${{ secrets.ABP_ACCESS_TOKEN_BIN }}" | base64 -d > access-token.bin
  

  4. Update your Dockerfile to copy the access-token.bin into the correct location inside the container:

  RUN mkdir -p /root/.abp/cli
     COPY access-token.bin /root/.abp/cli/access-token.bin
  

  5. Build your Docker image as usual. The ABP licensing check will now succeed inside the container.

  This approach is confirmed as the solution for running ABP commercial modules in Docker and CI/CD environments.

  Sources:

  • https://abp.io/support/questions/9263
  • https://abp.io/support/questions/6663
  • https://abp.io/support/questions/6508

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel