Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various unexpected problems #38

Open
snail2sky opened this issue Oct 28, 2024 · 0 comments
Open

Various unexpected problems #38

snail2sky opened this issue Oct 28, 2024 · 0 comments

Comments

@snail2sky
Copy link

such as fio, iperf.. etc
Your idea of ​​converting a docker image into a static executable file is simply genius. Unfortunately, the current adaptability is still very poor. I tested both and failed.

./dockerc_x86-64 --version
dockerc version: v0.3.2 (513216a)

build fio error

# build static binnary fio
./dockerc_x86-64 -i docker://xridge/fio -o fio --arch amd64
# execut it but raise error
./fio -direct=1 -iodepth=128 -rw=randread -ioengine=libaio -bs=4k -size=2G -numjobs=1 -runtime=30 -group_reporting -filename=/data0/test.file -name=Rand_Read_Testing -output=/tmp/fio_rand_read_output.json
fio: pid=0, err=2/file:filesetup.c:161, func=open, error=No such file or directory

build iperf error

# build static binnary iperf
# build static iperf
./dockerc_x86-64 -i docker://phlak/iperf -o iperf --arch amd64
# run daemon is ok
./iperf -s &
# but run client error
./iperf -c 127.0.0.1 
unknown argument ignored: lazytime
iperf3: parameter error - cannot be both server and client

I look forward to your great success with this project, because making a docker image is much easier than making an appimage, come on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant