/usr/share/sbt/bin/sbt-launch-lib.bash: line 58: 405 Killed "$@" | subprocess installed post-installation script returned error exit status 137
See original GitHub issuesteps
docker build --no-cache -t docker-play .
Dockerfile:
###########################################################
# Dockerfile to build PLAY Installed Containers
# Based on Ubuntu
############################################################
# Set the base image to Ubuntu
FROM ubuntu:latest
# File Author / Maintainer
MAINTAINER sfergusonvolute
# RUN apt-get install -y apt-transport-https
# Update the apt repository
RUN apt-get update
# Install necessary tools
RUN apt-get install -y apt-transport-https
RUN apt-get install -y apt-utils
RUN apt-get install -y docker
RUN apt-get install -y vim
RUN apt-get install -y ssh
RUN apt-get install -y dialog
RUN apt-get install -y net-tools
# Add sources
RUN echo "deb https://dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list
RUN apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 2EE0EA64E40A89B84B2DF73499E82A75642AC823
RUN apt-get update
# Upgrade the distro
#RUN apt-get dist-upgrade -y
# Install the requirements for the application
RUN apt-get install openjdk-8-jdk-headless -y
RUN apt-get install sbt -y
problem
I had no problems using docker to build my containers on Monday, but today I receive this error:
[warn] No sbt.version set in project/build.properties, base directory: /
/usr/share/sbt/bin/sbt-launch-lib.bash: line 58: 405 Killed "$@"
dpkg: error processing package sbt (--configure):
subprocess installed post-installation script returned error exit status 137
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for systemd (229-4ubuntu19) ...
Errors were encountered while processing:
sbt
E: Sub-process /usr/bin/dpkg returned an error code (1)
The command '/bin/sh -c apt-get install sbt -y' returned a non-zero code: 100
expectation
A successful unattended installation of sbt.
notes
sbt version: 0.13.16
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Error 137 - Killed · Issue #4192 · travis-ci ...
i believe the exit code of 137 suggests something did a kill -9 on the parent, i.e. the travis build script itself. @BanzaiMan...
Read more >bash error code 137 vs 1 when out of memory
Thus you get an exit of 137. 137 & 127 = 9, so the mono process was sent a SIGKILL signal (kill -9)...
Read more >Bugs : glibc package : Ubuntu
#1590744 package libc-bin 2.23-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135.
Read more >Scheduled tasks killed, return code 137 : Forums
My scheduled job was killed after 10248 seconds. Any plans to remove/extend it? Thanks! Yes, the limit is still in force.
Read more >Default exit code when process is terminated?
Thus in a shell script you cannot tell conclusively whether a command was killed by a signal or exited with a status code...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had same thing (exact message was like @SwapnilBorse123.
Based on above suggestions, i just increased allowable memory for docker (was at 2GiB before), and that worked fine.
I solved this issue I had with
sbt-1.1.5.deb
version by:Then, as I’m using java 8, I had to patch the following line so a memory limitation was applied during assembly: in
sbt/bin/sbt-launch-lib.bash
at line 90:As a note, watching memory consumption in htop, it was lower with
0.13.0
version.