Closed lrouhier closed 5 years ago
jcohenadad
commented
5 years ago @lrouhier your error verbose was not informative enough (you cut too much). I am able to reproduce this issue: (almost) full verbose here.
Looks like the problem is related to the download of SCT package from GH.
lrouhier
commented
5 years ago Yes i dont know if that is relevant but the https://github.com/neuropoly/spinalcordtoolbox/archive url lead to a page that does not exist.
jcohenadad
commented
5 years ago Exactly, i just found out that the 3.2.4 leads to a 404 error. The following command works:
curl --location https://github.com/neuropoly/spinalcordtoolbox/archive/4.0.0-beta.5.tar.gz | gunzip | tar x && cd spinalcordtoolbox-4.0.0-beta.5 && yes | ./install_sct && cd - && rm -rf spinalcordtoolbox-4.0.0-beta.5The problem was the "v" missing --> https://github.com/neuropoly/spinalcordtoolbox/archive/v3.2.4.tar.gz works
lrouhier
commented
5 years ago Alright. I'll try with that.
jcohenadad
commented
5 years ago i'm updating the doc
UPDATE: doc updated in f8f90a7
jcohenadad
commented
5 years ago OK, I tried with the corrected version name, but ran into the following error:
Done building images
ERROR:root:sct-v3.2.4-ubuntu-18.04 failed with error code 1
INFO:root:sct-v3.2.4-official finished successfully
[1, 0]
ERROR:root:Not proceeding further as one distro failedI tried with the corrected name for version 4 beta.5 and got a similar problem:
Successfully built 2ef77e689999
Successfully tagged sct-4.0.0-beta.5-ubuntu-18.04:latest
ERROR:root:sct-4.0.0-beta.5-official failed with error code 137
Done building images
INFO:root:sct-4.0.0-beta.5-ubuntu-18.04 finished successfully
ERROR:root:sct-4.0.0-beta.5-official failed with error code 137
[0, 137]
ERROR:root:Not proceeding further as one distro failedfull verbose (https://pastebin.com/GLxdUxh0)
jcohenadad
commented
5 years ago @zougloub is it expected to have the message "Not proceeding further as one distro failed" if only one distro was asked as output?
lrouhier
commented
5 years ago I launched the command to generate for all distro to try if it came from that. It is running right now.
jcohenadad
commented
5 years ago Regardless of this error, the folders of all distros are created locally and each includes a Dockerfile. So it is still possible to build a container using the following command:
docker build --no-cache -t poufpouf .Note: I am using the --no-cache flag here to avoid Docker reusing previous build, as mentioned in the sct-docker notes.
zougloub
commented
5 years ago @zougloub is it expected to have the message "Not proceeding further as one distro failed" if only one distro was asked as output?
An "official" build is added by the code... that logic should be improved.
zougloub
commented
5 years ago Is it possible the system ran out of RAM when building? Error code 137 (128 + 9) means it's been killed with signal 9 (SIGKILL), may have been killed during a build by the OOM ripper.
zougloub
commented
5 years ago @zougloub is it expected to have the message "Not proceeding further as one distro failed" if only one distro was asked as output?
An "official" build is added by the code... that logic should be improved.
(Fixed that thing)
zougloub
commented
5 years ago In case we're running a native Docker container not a VM, I've also made the command only build the official release by default. It was running several distros in a thread pool, and that may also put some memory pressure on the system.
zougloub
commented
5 years ago The wxPython build is RAM hungry (not a problem on that huge machine though):
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
a98c1dbc76a6 silly_bartik 1238.71% 2.286GiB / 503.9GiB 0.45% 70.8MB / 825kB 0B / 0B 105
1a16a47aa7e4 eager_shamir 982.45% 1.977GiB / 503.9GiB 0.39% 70.8MB / 796kB 127kB / 0B 100I was able to generate the tarball using commit 5ac66b84e13cd4887d96f0267704d5057b7b9a23 and the following command:
./sct_docker_images.py generate --version 62cc99396f6f213a0fcea94040ddf352019de6c7 --distros ubuntu:18.04 --generate-distro-specific-sct-tarballThank you @zougloub!
Description
The command given as example (./sct_docker_images.py generate --version 3.2.4 --distros ubuntu:18.04 --generate-distro-specific-sct-tarball) does not create an offline tarball
Steps to Reproduce
Mac OS Mojave . sct_docker repo cloned on 1 august 2019.
run' ./sct_docker_images.py generate --version 3.2.4 \ --distros ubuntu:18.04 \ --generate-distro-specific-sct-tarball'
Expected behavior: create sct offline archive for version 3.2.4
Actual behavior: creation of dockerFiles. Error near the end of the program .
The error is the following