slimtoolkit / slimtoolkit/slim
Ubuntu 23.10 slim build error docker socket not found
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 841
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
"sudo slim --log-level=trace build streamlit_app_image" make slimmed container
Actual Behavior
(.venv) aitalent@aitalent-1-0:~/Code/streamlit_app$ sudo slim --log-level=trace build streamlit_app_image
[sudo] password for aitalent:
time="2023-12-20T18:57:13+05:00" level=debug msg="sysinfo => system.SystemInfo{Sysname:"Linux", Nodename:"aitalent-1-0", Release:"6.5.0-14-generic", Version:"#14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023", Machine:"x86_64", Domainname:"(none)", OsBuild:"", Distro:system.DistroInfo{Name:"Ubuntu", Version:"23.10", DisplayName:"Ubuntu 23.10"}}"
time="2023-12-20T18:57:13+05:00" level=debug msg="param.error.app.options - no app params"
cmd=build info=param.http.probe message='using default probe'
time="2023-12-20T18:57:13+05:00" level=debug msg="customImageTag='', additionalTags=[]string(nil)" app=slim cmd=build
cmd=build info=report file='slim.report.json'
time="2023-12-20T18:57:13+05:00" level=fatal msg=terminating error="docker socket not found" stack="goroutine 1 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x5e\ngithub.com/slimtoolkit/slim/pkg/app.(*ExecutionContext).FailOn(0xc00068a4c0, {0x2262fe0, 0xc0003f7be0})\n\tgithub.com/slimtoolkit/slim/pkg/app/execontext.go:58 +0x58\ngithub.com/slimtoolkit/slim/pkg/app/master/command/build.OnCommand(_, , {, _}, , {, }, {, _}, {0x0, ...}, ...)\n\tgithub.com/slimtoolkit/slim/pkg/app/master/command/build/handler.go:208 +0x997\ngithub.com/slimtoolkit/slim/pkg/app/master/command/build.glob..func1(0xc0003c1280)\n\tgithub.com/slimtoolkit/slim/pkg/app/master/command/build/cli.go:751 +0x5e10\ngithub.com/urfave/cli/v2.(*Command).Run(0x327eb00, 0xc0002d0680)\n\tgithub.com/urfave/cli/v2@v2.3.0/command.go:163 +0x583\ngithub.com/urfave/cli/v2.(*App).RunContext(0xc000103520, {0x2280768?, 0x32f1ec0}, {0xc000050080, 0x4, 0x4})\n\tgithub.com/urfave/cli/v2@v2.3.0/app.go:313 +0xaa5\ngithub.com/urfave/cli/v2.(*App).Run(...)\n\tgithub.com/urfave/cli/v2@v2.3.0/app.go:224\ngithub.com/slimtoolkit/slim/pkg/app/master.Run()\n\tgithub.com/slimtoolkit/slim/pkg/app/master/app.go:15 +0x45\nmain.main()\n\tgithub.com/slimtoolkit/slim/cmd/slim/main.go:15 +0x187\n"
Steps to Reproduce the Problem
link on zipped container
https://drive.google.com/file/d/1J45h66ZebZ51W4knlOUh4909QQRuL3-X/view?usp=sharing
sudo slim --log-level=trace build streamlit_app_image
Specifications
{
"version": "1.1",
"engine": "linux/amd64|Transformer|1.40.7|fc2a26643f26cde441afb267b5a0a17bddc9a897|2023-12-10_07:50:14AM",
"containerized": false,
"host_distro": {
"name": "Ubuntu",
"version": "23.10",
"display_name": "Ubuntu 23.10"
},
"type": "build",
"state": "error",
"target_reference": "streamlit_app_image",
"system": {
"type": "",
"release": "",
"distro": {
"name": "",
"version": "",
"display_name": ""
}
},
"source_image": {
"identity": {
"id": ""
},
"size": 0,
"size_human": "",
"create_time": "",
"docker_version": "",
"architecture": "",
"container_entry": {
"exe_path": ""
}
},
"minified_image_size": 0,
"minified_image_size_human": "",
"minified_image": "",
"minified_image_has_data": false,
"minified_by": 0,
"artifact_location": "",
"container_report_name": "",
"seccomp_profile_name": "",
"apparmor_profile_name": "",
"image_stack": null,
"image_created": false,
"image_build_engine": ""
}
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 at pkg/app/master/command/build/handler.go:208, where the stack trace reports the build failure, and trace how the build command locates the Docker socket. Reproduce the command on Ubuntu 23.10 with the supplied container, then verify the behavior after the socket-not-found failure is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, ubuntu
- Domain
- cli, devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100