Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot build RaspCli inside the cpu Dockerfile

See original GitHub issue

I followed the installation guide for Docker cpu and can successfully go inside the container and run the tests.

The tutorial has a part that says start an RP server. I can’t do this because I don’t have ./serving/build/RaspCli.

To build RaspCli I ran the following commands inside ./serving/build:

wget https://download.pytorch.org/libtorch/cpu/libtorch-cxx11-abi-shared-with-deps-1.3.0%2Bcpu.zip -O libtorch.zip && \
    unzip libtorch.zip && \
    rm libtorch.zip

conda install glog

apt -y install libgflags-dev \
                   libgoogle-glog-dev \
                   libboost-tools-dev \
                   libboost-thread1.62-dev

cmake -DCMAKE_PREFIX_PATH=$HOME/libtorch ..
make

The build fails with many multiple definitions error. Here is an excerpt:

/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o): In function `__morestack_large_model':
(.text+0x11c): multiple definition of `__morestack_large_model'
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o):(.text+0x11c): first defined here
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o): In function `__stack_split_initialize':
(.text+0x12c): multiple definition of `__stack_split_initialize'
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o):(.text+0x12c): first defined here
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o): In function `__morestack_get_guard':
(.text+0x155): multiple definition of `__morestack_get_guard'
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o):(.text+0x155): first defined here
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o): In function `__morestack_set_guard':
(.text+0x15f): multiple definition of `__morestack_set_guard'
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o):(.text+0x15f): first defined here
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o): In function `__morestack_make_guard':
(.text+0x169): multiple definition of `__morestack_make_guard'
/usr/lib/gcc/x86_64-linux-gnu/7/libgcc.a(morestack.o):(.text+0x169): first defined here
collect2: error: ld returned 1 exit status
CMakeFiles/RaspCli.dir/build.make:106: recipe for target 'RaspCli' failed
make[2]: *** [RaspCli] Error 1
CMakeFiles/Makefile2:110: recipe for target 'CMakeFiles/RaspCli.dir/all' failed
make[1]: *** [CMakeFiles/RaspCli.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

How can I successfully build ReAgent inside the CPU Docker container?

I am running Ubuntu 18.04.3 LTS.

Issue Analytics

State:
Created 4 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

1reaction

hsm207commented, Nov 29, 2019

@amarchin You are welcome.

I’ve made PR #190 to fix the error in the Docker section.

0reactions

amarchincommented, Nov 29, 2019

@hsm207

You’re right, thank you. There is an error in the installation.rst file in the Docker section then.

Top Results From Across the Web

docker build - Docker Documentation

The docker build command builds Docker images from a Dockerfile and a “context”. A build's context is the set of files located in...

Runtime options with Memory, CPUs, and GPUs

Docker provides ways to control how much memory, or CPU a container can use, setting runtime configuration flags of the docker run command....

docker builder build

docker builder build: Build an image from a Dockerfile. ... --cpuset-cpus, CPUs in which to allow execution (0-3, 0,1). --cpuset-mems, MEMs in which...

Image-building best practices - Docker Documentation

Tips for building the images for our application. ... For example, to scan the getting-started image you created earlier in the tutorial, you...

Faster Multi-Platform Builds: Dockerfile Cross-Compilation ...

In order to build multi-platform container images, ... binaries for its native architecture. x86 CPU can't run ARM binaries and vice versa.