Mattias Wadman
Mattias Wadman
Hello, think i have the same or similar issue when i try to compile projects that relay on `/proc/cpuinfo` to detect CPU features (for example https://github.com/georgmartius/vid.stab/blob/e851e7b11c482c116d22b247821f22862a207245/CMakeModules/FindSSE.cmake#L7). Im using docker for...
As i understand it docker buildx only emulates user-land processes so /proc in the container will still be a proc filesystem from the host kernel.
This is from a amd64 macbook docker desktop `docker run -ti --rm --platform linux/arm64 alpine:3.16.1` container: ``` / # lscpu | grep -i arch Architecture: aarch64 / # grep -i...
Yeap `uname -m` seems to work, but i'm not sure that is the case for other container runtimes when doing emulation.
Ok, but no sure i understand your use-case. Reading /proc/cpuinfo will not fail in the case you'r inside an emulated container, it will just return the host's cpu info.
I do something like this is read and pass envionment variables: ``` { prep: HELLO="hello $USER" sh -c 'echo $HELLO' } ```
I see, would `prep: cd "$GOPATH/bin" && ...` work?
Yes i've noticed this also. Would what be a nice way to configure it? all parameters configurable or only max? thru argument or config files? both?
Can you post the full modd.conf? running modd from modd?
Maybe could try `exec docker run ....` if the shell is not forwarding the signal to docker. Also could try set `@shell = bash` and use `exec`