[Feature] Improve the compilation of skywalking-rover

[tsint]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

When compiling skywalking-rover, add buildvcs=false to prevent compilation failures caused by Git in container environments. Additionally, include the flags -tags osusergo,netgo to achieve fully static compilation, avoiding runtime issues caused by incompatible versions of the glibc library.

For more infomation, see:

• Google Groups: golang-nuts
• Radhifadlillah Blog: Build Go Statically

Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[mrproliu]

1. For buildvcs=false, could you describe the scenario when it would cause failure? We already use volume mount when building the binary in the container.
2. For the -tags osusergo,netgo, we already disable the gclib library in https://github.com/apache/skywalking-rover/blob/main/docker/Dockerfile.build#L26. So I think these two tags are not necessary.

[tsint]

1. For buildvcs=false, could you describe the scenario when it would cause failure? We already use volume mount when building the binary in the container.
2. For the -tags osusergo,netgo, we already disable the gclib library in https://github.com/apache/skywalking-rover/blob/main/docker/Dockerfile.build#L26. So I think these two tags are not necessary.

1. Many scenarios could lead to issues, such as the code directory not being set as a safe.directory, a change in the directory owner. Or the presence of a .git directory in a parent directory, or corruption of the .git directory itself. In short, setting this causes no harm and helps avoid unnecessary compilation failures.
2. Based on my actual execution of the ldd command, it does not appear to be as you described.

$ ldd bin/skywalking-rover-latest-linux-amd64
        linux-vdso.so.1 (0x00007ffc287e8000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faeb7800000)
        /lib64/ld-linux-x86-64.so.2 (0x00007faeb7b93000)

If go tags are added, it becomes noticeably different.

$ ldd bin/skywalking-rover-latest-linux-amd64
        not a dynamic executable

Setting ENV CGO_ENABLED=0 has no effect on Docker's RUN command. Moreover, if CGO_ENABLED=0 is added to the compilation command, importing "c" will result in a compilation failure.

[mrproliu]

Many scenarios could lead to issues, such as the code directory not being set as a safe.directory, a change in the directory owner. Or the presence of a .git directory in a parent directory, or corruption of the .git directory itself. In short, setting this causes no harm and helps avoid unnecessary compilation failures.

Make sense to me, please add this parameter.

Setting ENV CGO_ENABLED=0 has no effect on Docker's RUN command. Moreover, if CGO_ENABLED=0 is added to the compilation command, importing "c" will result in a compilation failure.

Then, we should consider why the CGO_ENABLED is not working?