slimtoolkit / slimtoolkit/slim

not found in PATH

Open
#176 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
Go
Stars
23.4k
Forks
840
PR merge metrics
No merged PRs in 30d

Description

This is a great tool, I use it a lot in production.
With web apps I use it very well. But for non-web applications I sometimes get errors. This is an application I built with no success
I use this repo to build docker https://github.com/evait-security/docker-multitor

This is the command I use
build --target multitor:latest --http-probe false --include-path /lib/ld-musl-x86_64.so.1 --include-path /lib/libz.so.1 --include-path /usr/lib/libpcre.so.1 --include-path /usr/lib/libpcreposix.so.0 --include-path /lib/libssl.so.1.1 --include-path /lib/libcrypto.so.1.1 --include-path /usr/lib/liblua-5.3.so.0 --include-path /usr/lib/libevent-2.1.so.7 --include-path /usr/lib/liblzma.so.5 --include-path /usr/lib/libzstd.so.1 --include-path /lib/libprocps.so.8 --include-path /usr/lib/libbrotlienc.so.1 --include-path /usr/lib/libcares.so.2 --include-path /usr/lib/libnghttp2.so.14 --include-path /usr/lib/libstdc++.so.6 --include-path /usr/lib/libgcc_s.so.1 --include-path /lib/ld-musl-x86_64.so.1 --include-path /usr/lib/libbrotlicommon.so.1 --include-path /usr/lib/libintl.so.8 --include-path /var/lib/multitor --include-path /multitor --include-bin /usr/sbin/privoxy --include-bin /usr/sbin/haproxy --include-bin /usr/bin/tor --include-bin /usr/bin/nc --include-bin /usr/local/bin/polipo --include-bin /usr/local/bin/multitor --include-bin /usr/bin/hpts --include-bin /bin/ps --include-bin /usr/bin/node --include-bin /usr/bin/npm --workdir /multitor --cmd './startup.sh'

When the build is finished I run docker and get an error not found in PATH: sudo hpts

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported Docker build and run command against the linked docker-multitor project, using startup.sh as the entry point. Trace why hpts is reported as missing from PATH after the image is built, and confirm the container can start successfully with the requested binaries available.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.