dockerd: Build failure on mips64_octeonplus
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @G-M0N3Y-2503
Environment: mips64_octeonplus, snapshot
Description:
Buildbots are getting an error when building dockerd for mips64_octeonplus, from the faillog:
---> Making bundle: binary (in bundles/binary)
Building static bundles/binary-daemon/dockerd (linux/mips64)...
# github.com/docker/docker/vendor/github.com/moby/buildkit/snapshot
.go_work/build/src/github.com/docker/docker/vendor/github.com/moby/buildkit/snapshot/diffapply_unix.go:131:8: cannot use stat.Dev (variable of type uint32) as uint64 value in struct literal
.go_work/build/src/github.com/docker/docker/vendor/github.com/moby/buildkit/snapshot/diffapply_unix.go:301:12: cannot use unix.Mkdev(0, 0) (value of type uint64) as uint32 value in struct literal
make[3]: *** [Makefile:186: /builder/shared-workdir/build/sdk/build_dir/target-mips64_octeonplus_64_musl/dockerd-24.0.2/.built] Error 1
time: package/feeds/packages/dockerd/compile#208.06#49.39#224.30
The makefile excludes mips/mipsel but not mips64/mips64el - should the makefile be updated to exclude mips64 or should can this build error be fixed?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dockerd Makefile exclusion at the linked line and the mips64 compile errors in vendor/github.com/moby/buildkit/snapshot/diffapply_unix.go, using the linked faillog as the failure reference. Determine whether the package should exclude mips64 or whether the build error can be fixed, then verify the chosen resolution with a successful mips64_octeonplus build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100