search

openshift / source-to-image

A tool for building artifacts from source and injecting into container images
Apache License 2.0
2.46k stars 697 forks source link

S2i killed #1051

Closed narennadig closed 3 years ago

narennadig commented 4 years ago 
(base) [narendranath24 ~]$ s2i
Killed

I keep getting this error when using s2i..How do I fix it?

adambkaplan commented 4 years ago

@narennadig which operating system are you using? Are you able to run s2i version?

narennadig commented 4 years ago

Red Hat Enterprise Linux Workstation release 7.8 (Maipo) @adambkaplan I'm not able to run s2i version as well..same error

adambkaplan commented 4 years ago

@narennadig do you recall how you installed s2i - did you download from GitHub or yum install an rpm?

narennadig commented 4 years ago

I think rpm ... Should I re install it?

adambkaplan commented 4 years ago

The rpm shipped in RHEL is older and is not maintained by this project. You can file a Bugzilla to see if it can be upgraded to the latest release.

EDIT - I discovered s2i is on v1.1.13, which isn't drastically old.

https://access.redhat.com/downloads/content/source-to-image/1.1.13-1.el7/x86_64/fd431d51/package

adambkaplan commented 4 years ago

Note that the s2i RPM requires docker, which may not be present on RHEL 7.8 machines.

kstephen314159 commented 4 years ago

I have this problem too but (1) I get it when running the "help" command and (2) I installed from tar.gz

[zaphod@oc6010654212 ocp-tools]$ tar -xvzf ~/Downloads/source-to-image-v1.3.0-eed2850f-linux-386.tar.gz ./ ./sti ./s2i [zaphod@oc6010654212 ocp-tools]$ ./s2i Source-to-image (S2I) is a tool for building repeatable docker images.

A command line interface that injects and assembles source code into a docker image. Complete documentation is available at http://github.com/openshift/source-to-image

Usage: s2i [flags] s2i [command]

Available Commands: build Build a new image completion Generate completion for the s2i command (bash or zsh) create Bootstrap a new S2I image repository generate Generate a Dockerfile using an existing S2I builder image that can be used to produce an image by any application supporting the format. rebuild Rebuild an existing image usage Print usage of the assemble script associated with the image version Display version

Flags: --ca string Set the path of the docker TLS ca file (default "/home/zaphod/.docker/ca.pem") --cert string Set the path of the docker TLS certificate file (default "/home/zaphod/.docker/cert.pem") -h, --help help for s2i --key string Set the path of the docker TLS key file (default "/home/zaphod/.docker/key.pem") --loglevel int32 Set the level of log output (0-5) --tls Use TLS to connect to docker; implied by --tlsverify --tlsverify Use TLS to connect to docker and verify the remote -U, --url string Set the url of the docker socket to use (default "unix:///var/run/docker.sock")

Use "s2i [command] --help" for more information about a command. [zaphod@oc6010654212 ocp-tools]$ ./s2i help completion Killed [zaphod@oc6010654212 ocp-tools]$ ./s2i help build Killed [zaphod@oc6010654212 ocp-tools]$ ./s2i completion Killed

RHEL 7.8

kstephen314159 commented 4 years ago

I use podman instead of docker. Does s2i work with podman? Is that the problem?

kstephen314159 commented 4 years ago

Well that was embarrassing. As you may have noticed from the output I included, I had accidentally tried the 386 version instead of the 64-bit one. The amd64 build works fine.

adambkaplan commented 4 years ago

I use podman instead of docker. Does s2i work with podman? Is that the problem?

Unfortunately most s2i build commands do not work without docker. The exceptions are s2i build --as-dockerfile and s2i generate. We've previously that we need to remove our explicit dependency on docker (see #966)

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/source-to-image/issues/1051#issuecomment-782575245): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.