AI Features like Intellience, MCP disappear after rebuild with plugins

[mike-brown8]

Describe the bug

When I rebuild binary with plugins with this command:

./answer build --with github.com/apache/answer-plugins/connector-basic --with github.com/apache/answer-plugins/reviewer-baidu --with github.com/apache/answer-plugins/reviewer-basic --with github.com/apache/answer-plugins/storage-s3 --with github.com/apache/answer-plugins/storage-aliyunoss --with github.com/apache/answer-plugins/storage-tencentyuncos --with github.com/apache/answer-plugins/search-algolia --with github.com/apache/answer-plugins/quick-links --with github.com/apache/answer-plugins/render-markdown-codehighlight --with github.com/apache/answer-plugins/captcha-basic --with github.com/apache/answer-plugins/captcha-google-v2 --with github.com/apache/answer-plugins/connector-dingtalk --with github.com/apache/answer-plugins/notification-dingtalk --with github.com/mike-brown8/answer-connector-furtv/connector-vds

The AI Features disappear from the manage page.

To Reproduce

Steps to reproduce the behavior:

1. Download v2.0.0 linux amd64 binary from the offical repo.
2. Install it and run it.
3. After init, you can see Intellience TAB in the manage page.
4. Stop it then run rebuild command above.
5. Run it again.
6. The Intellience TAB disappears and cannot also being called via HOST/admin/mcp.

Expected behavior

The Intellience feature works well.

Screenshots

Platform

• Device: Simpcloud.cn VPS
• OS: Ubuntu 22 LTS
• Browser and version: New Edge on Windows
• Version: 2.0.0

[LinkinStars]

Thank you for your feedback. Please try adding an environment variable like ANSWER_MODULE=github.com/apache/answer@v2.0.0 at the beginning of the command and see if it packages correctly.

[mike-brown8]

Thank you for your feedback. Please try adding an environment variable like ANSWER_MODULE=github.com/apache/answer@v2.0.0 at the beginning of the command and see if it packages correctly.

Unfortunately, the command runs failed.

The terminal screenshot below:

[LinkinStars]

Thank you very much for the feedback; there is indeed an issue with the binary. This is the same problem as the one described at #1514.

[r3f]

You can verify the exact commit used in the official image with:

docker inspect apache/answer | grep -A5 "Labels"

Example output:

"Labels": {
    "maintainer": "linkinstar@apache.org",
    "org.opencontainers.image.created": "2026-02-03T02:01:49.647Z",
    "org.opencontainers.image.description": "A Q&A platform software for teams at any scales. Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer.",
    "org.opencontainers.image.licenses": "Apache-2.0",
    "org.opencontainers.image.revision": "a6bfd402b68091b4e84f98255c48caa9dbefe17d"
}

Then, when building with plugins, make sure you use the same revision:

RUN ANSWER_MODULE=github.com/apache/answer@a6bfd402b68091b4e84f98255c48caa9dbefe17d answer build

Also ensure your build stage uses a compatible Go version, for example:

FROM golang:1.24-alpine AS golang-builder

This keeps your custom build aligned with the official image and helps avoid unexpected compatibility issues.

[mike-brown8]

You can verify the exact commit used in the official image with:

docker inspect apache/answer | grep -A5 "Labels"

Example output:

"Labels": {
    "maintainer": "linkinstar@apache.org",
    "org.opencontainers.image.created": "2026-02-03T02:01:49.647Z",
    "org.opencontainers.image.description": "A Q&A platform software for teams at any scales. Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer.",
    "org.opencontainers.image.licenses": "Apache-2.0",
    "org.opencontainers.image.revision": "a6bfd402b68091b4e84f98255c48caa9dbefe17d"
}

Then, when building with plugins, make sure you use the same revision:

RUN ANSWER_MODULE=github.com/apache/answer@a6bfd402b68091b4e84f98255c48caa9dbefe17d answer build

Also ensure your build stage uses a compatible Go version, for example:

FROM golang:1.24-alpine AS golang-builder

This keeps your custom build aligned with the official image and helps avoid unexpected compatibility issues.

It works, thank you!!!

[littleyz]

You can verify the exact commit used in the official image with:

docker inspect apache/answer | grep -A5 "Labels"
Example output:

"Labels": {
"maintainer": "linkinstar@apache.org",
"org.opencontainers.image.created": "2026-02-03T02:01:49.647Z",
"org.opencontainers.image.description": "A Q&A platform software for teams at any scales. Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer.",
"org.opencontainers.image.licenses": "Apache-2.0",
"org.opencontainers.image.revision": "a6bfd402b68091b4e84f98255c48caa9dbefe17d"
}
Then, when building with plugins, make sure you use the same revision:

RUN ANSWER_MODULE=github.com/apache/answer@a6bfd40 answer build
Also ensure your build stage uses a compatible Go version, for example:

FROM golang:1.24-alpine AS golang-builder
This keeps your custom build aligned with the official image and helps avoid unexpected compatibility issues.

Using the latest docker (version 2.0.0) to build a plugin version, I will have the same problem, AI Features like Intellience and MCP disappear, what should I do?