Unable to run demo application

Expected Behavior

Be able to run demo application

Actual Behavior

Demo steps fail with error

Steps to Reproduce the Problem

1. git clone https://github.com/slimtoolkit/examples.git
2. cd examples/node_ubuntu
3. docker build -t my/sample-node-app .
4. slim build my/sample-node-app

slim build my/sample-node-app app='slim' message='Join the Gitter channel to ask questions or to share your feedback' info='https://gitter.im/docker-slim/community' app='slim' message='Join the Discord server to ask questions or to share your feedback' info='https://discord.gg/9tDyxYS' app='slim' message='GitHub Discussions' info='https://github.com/slimtoolkit/slim/discussions' cmd=build info=param.http.probe message='using default probe' cmd=build state=started cmd=build info=params rt.as.user='true' keep.perms='true' tags='' target.type='image' target='my/sample-node-app' continue.mode='probe' cmd=build state=image.inspection.start cmd=build info=image id='sha256:e176f589144b1c3a44ac0c50496399baf37e6dcd6411a0d4e8295bd16f730294' size.bytes='414788140' size.human='415 MB' cmd=build info=image.stack index='0' name='ubuntu:14.04' id='sha256:13b66b487594a1f2b75396013bc05d29d9f527852d96c5577cc4f187559875d0' cmd=build info=image.stack index='1' name='my/sample-node-app:latest' id='sha256:e176f589144b1c3a44ac0c50496399baf37e6dcd6411a0d4e8295bd16f730294' cmd=build info=image.exposed_ports list='1300' cmd=build state=image.inspection.done cmd=build state=container.inspection.start cmd=build info=container id='c5b8b6bd24c0ae82ae3f695690e30b6c03118572b6751dd36848f33bc8f30846' status='created' name='slimk_967928_20230801152718' cmd=build info=container name='slimk_967928_20230801152718' id='c5b8b6bd24c0ae82ae3f695690e30b6c03118572b6751dd36848f33bc8f30846' status='running' cmd=build info=container message='obtained IP address' ip='101.10.0.5' time="2023-08-01T11:28:27-04:00" level=error msg="channel.NewCommandClient: NewClient error = wait timeout" time="2023-08-01T11:28:27-04:00" level=error msg="ipc.NewClient init error = wait timeout" cmd=build info=report file='slim.report.json' time="2023-08-01T11:28:27-04:00" level=fatal msg="slim: failure" error="wait timeout" stack="goroutine 1 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x65\ngithub.com/docker-slim/docker-slim/pkg/util/errutil.FailOn({0x1f9fa00, 0xc0003cd0f0})\n\tgithub.com/docker-slim/docker-slim/pkg/util/errutil/errutil.go:32 +0x5e\ngithub.com/docker-slim/docker-slim/pkg/app.(*ExecutionContext).FailOn(0xc0004c2580?, {0x1f9fa00?, 0xc0003cd0f0?})\n\tgithub.com/docker-slim/docker-slim/pkg/app/execontext.go:56 +0x49\ngithub.com/docker-slim/docker-slim/pkg/app/master/commands/build.OnCommand(_, _, {_, _}, _, {_, _}, {_, _}, {0x0, ...}, ...)\n\tgithub.com/docker-slim/docker-slim/pkg/app/master/commands/build/handler.go:1121 +0x440b\ngithub.com/docker-slim/docker-slim/pkg/app/master/commands/build.glob..func1(0xc0004eba80)\n\tgithub.com/docker-slim/docker-slim/pkg/app/master/commands/build/cli.go:744 +0x5e90\ngithub.com/urfave/cli/v2.(*Command).Run(0x2dd7e20, 0xc0004b94c0)\n\tgithub.com/urfave/cli/v2@v2.3.0/command.go:163 +0x5c8\ngithub.com/urfave/cli/v2.(*App).RunContext(0xc000503040, {0x1fb9118?, 0xc0000480e0}, {0xc00003e090, 0x3, 0x3})\n\tgithub.com/urfave/cli/v2@v2.3.0/app.go:313 +0xb36\ngithub.com/urfave/cli/v2.(*App).Run(...)\n\tgithub.com/urfave/cli/v2@v2.3.0/app.go:224\ngithub.com/docker-slim/docker-slim/pkg/app/master.Run()\n\tgithub.com/docker-slim/docker-slim/pkg/app/master/app.go:15 +0x46\nmain.main()\n\tgithub.com/docker-slim/docker-slim/cmd/slim/main.go:15 +0x18c\n" version="linux|Transformer|1.40.2|latest|latest"

Specifications

• Version: 1.40.2
• Platform: CentOS
• Working on a corporate network that blocks access to unknown urls

This is the first time I'm using slim, I started with my own image by got the above error so thought maybe I could run the demo first and see if it works (it didn't).

Start by reproducing the listed examples/node_ubuntu steps on the stated CentOS and corporate network setup, then read the failure path in pkg/app/master/commands/build/handler.go and the command wiring in cli.go. Determine what causes the wait timeout during container inspection; done means the demo completes successfully or the failure has a documented, actionable reproduction and diagnosis.