[转帖]SPEC2006移入docker后的运行问题

spec2006,移入,docker,运行,问题 · 浏览次数 : 0

小编点评

The error message indicates that the `runspec` command is not found in the specified directory. This is likely because the `runspec` binary is not installed in the Docker container. **Possible solutions:** 1. **Ensure that the `runspec` binary is installed in the Docker container.** * You can install it using the `apk` package manager: ```docker run -it --rm --cpuset-cpus=1 spec /bin/bash ``` * Alternatively, you can build the binary from source: ```docker build -t my-image . ``` 2. **Verify that the `shrc` file is located in the Docker container.** * Check if the file is present in the container's working directory. * If it's not there, you may need to copy it manually. 3. **Check the permissions of the `shrc` file.** * Ensure that the `shrc` file has proper permissions (readable and executable). 4. **Use the `RUN` command to copy the `shrc` file into the container.** ```docker run -it --rm --cpuset-cpus=1 spec \ COPY /path/to/shrc/runspec /root/runspec \ CMD ["runspec"] ``` 5. **Restart the container after making changes to the `shrc` file.** **Additional notes:** * The `docker build` command assumes that the Dockerfile is located in the same directory as the `RUN` command. * If the `shrc` file requires specific environment variables, you may need to set them manually before running the container. * Ensure that the `runspec` binary is compatible with the Docker version being used.

正文

https://www.cnblogs.com/csxyc/p/7157890.html

实验需要给SPEC2006的benchmark绑定CPUID，于是想到用docker分配CPU资源，写一个简单的DOCKERFILE文件完成配置

1 FROM cmbant/docker-gcc-build
2 MAINTAINER jsbyxyc@me.com
3 
4 COPY cpu2006 /benchmarks/cpu2006
5 WORKDIR /benchmarks/cpu2006
6 CMD ['runspec']

然后运行

docker build -t [image name] .

之后执行

docker run -it --rm --cpuset-cpus=1 spec /bin/bash

进入docker中命令行

执行

source shrc
runspec --noreportable bzip2

出现错误 bad interpreter: No such file or directory

官方论坛中找到解决方法，具体描述如下：

runspec.02 q. Why am I getting messages about `specperl: bad interpreter`? For example:

bash: /cpu2006newdir/bin/runspec: /cpu2006/bin/specperl: bad interpreter: No such file or directory

a. Did you move the directory where runspec was installed? If so, you can probably put everything to rights, just by going to the new top of the directory tree and typing "bin/relocate".

For example, the following unwise sequence of events is repaired after completion of the final line.

Top of SPEC benchmark tree is '/cpu2006'
Everything looks okay.  cd to /cpu2006,
source the shrc file and have at it!
$ cd /cpu2006
$ . ./shrc
$ cd ..
$ mv cpu2006 cpu2006newdir
$ runspec -h | head
bash: runspec: command not found
$ cd cpu2006newdir/
$ . ./shrc
$ runspec --help | head
bash: /cpu2006newdir/bin/runspec: /cpu2006/bin/specperl: bad interpreter: No such file or directory
$ bin/relocate

运行bin/relocate即可恢复正确路径。