adding .dockerignore file to fix git submodule builds

[jrynkiew]

Description

The issue occurs when iotex-core is used as a submodule of a project. The Dockerfile copies the entire contents of the iotex-core folder into itself, but if it is added as a submodule, the parent of the git repository is incorrectly determined. If this fix is not applied, the following error occurs.

[build 8/8] RUN mkdir -p /go/pkg/linux_amd64/github.com/iotexproject/ && make clean build-all:
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.681 error obtaining VCS status: exit status 128
#0 0.681 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 0.999 error obtaining VCS status: exit status 128
#0 0.999 Use -buildvcs=false to disable VCS stamping.
#0 1.001 fatal: not a git repository: /go/apps/iotex-core/../../.git/modules/external/iotex-core
#0 1.002 fatal: not a git repository: /go/apps/iotex-core/../../.git/modules/external/iotex-core
#0 1.002 fatal: not a git repository: /go/apps/iotex-core/../../.git/modules/external/iotex-core
#0 1.007 Cleaning...
#0 1.021 go build -ldflags "-X 'github.com/iotexproject/iotex-core/pkg/version.PackageVersion=' -X 'github.com/iotexproject/iotex-core/pkg/version.PackageCommitID=' -X 'github.com/iotexproject/iotex-core/pkg/version.GitStatus="clean"' -X 'github.com/iotexproject/iotex-core/pkg/version.GoVersion=go version go1.18.5 linux/amd64' -X 'github.com/iotexproject/iotex-core/pkg/version.BuildTime=2022-11-06-UTC/18:41:39' -s -w" -o ./bin/ioctl -v ./tools/ioctl
#0 1.202 # cd /go/apps/iotex-core; git status --porcelain
#0 1.202 fatal: not a git repository: /go/apps/iotex-core/../../.git/modules/external/iotex-core
#0 1.202 error obtaining VCS status: exit status 128
#0 1.202 Use -buildvcs=false to disable VCS stamping.
#0 1.204 make: *** [Makefile:233: ioctl] Error 1

failed to solve: executor failed running [/bin/sh -c mkdir -p $GOPATH/pkg/linux_amd64/github.com/iotexproject/ && make clean build-all]: exit code: 2

Fixes #(issue)

Type of change

Please delete options that are not relevant.

• [] New feature (non-breaking change which adds functionality)

Adds functionality of allowing to use iotex-core as a submodule

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [] make test

Test Configuration:
System Information for: JEREMI
Manufacturer: Micro-Star International Co., Ltd.
Model: MS-7C31
CPU: Intel(R) Core(TM) i7-9700F CPU @ 3.00GHz
HDD Capacity: 310.31GB
HDD Space: 32.91% Free (102.11GB)
RAM: 15.94GB
Operating System: Microsoft Windows 11 Home, Service Pack: 0

running in WSL2 Ubuntu

Checklist:

• [] My code follows the style guidelines of this project
• [] I have performed a self-review of my code
• [] I have commented my code, particularly in hard-to-understand areas
• [] I have made corresponding changes to the documentation
• [] My changes generate no new warnings
• [] I have added tests that prove my fix is effective or that my feature works
• [] New and existing unit tests pass locally with my changes
• [] Any dependent changes have been merged and published in downstream modules

[Liuhaai]

add a new line

[Liuhaai]

.git/ or .git?

[codecov]

Codecov Report

Merging #3689 (86ad2aa) into master (263ff82) will decrease coverage by 0.77%.
The diff coverage is 88.80%.

@@            Coverage Diff             @@
##           master    #3689      +/-   ##
==========================================
- Coverage   74.47%   73.69%   -0.78%     
==========================================
  Files         269      276       +7     
  Lines       23925    24130     +205     
==========================================
- Hits        17818    17783      -35     
- Misses       5174     5440     +266     
+ Partials      933      907      -26     

Impacted Files	Coverage Δ
action/protocol/staking/candidate_statereader.go	53.94% <ø> (-3.38%)	⬇️
db/db_bolt.go	68.53% <0.00%> (-3.60%)	⬇️
ioctl/newcmd/action/actiontransfer.go	100.00% <ø> (ø)
ioctl/newcmd/action/stake2withdraw.go	95.74% <ø> (ø)
ioctl/newcmd/action/xrc20transferfrom.go	100.00% <ø> (ø)
ioctl/newcmd/did/didgethash.go	100.00% <ø> (ø)
ioctl/newcmd/did/didgeturi.go	100.00% <ø> (ø)
server/itx/server.go	62.20% <ø> (+2.20%)	⬆️
action/protocol/staking/handlers.go	74.47% <33.33%> (-0.64%)	⬇️
ioctl/newcmd/did/didgenerate.go	83.67% <83.67%> (ø)
... and 17 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information