Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to a smaller base image for jx #4481

Closed
hferentschik opened this issue Jun 28, 2019 · 8 comments
Closed

Switch to a smaller base image for jx #4481

hferentschik opened this issue Jun 28, 2019 · 8 comments
Labels
kind/enhancement An enhancement of an existing feature lifecycle/rotten

Comments

@hferentschik
Copy link

The default image used for the jx image is centos:7 which clocks in at around 200 MB. It would be nice to have a smaller base image, eg alpine or busybox.

There are concerns around alpine and DNS resolution though - gliderlabs/docker-alpine#255

@hferentschik hferentschik added the kind/enhancement An enhancement of an existing feature label Jun 28, 2019
@hferentschik
Copy link
Author

See also discussion on this pull request - https://github.com/jenkins-x/jx/pull/4412/files#r298096706

@hferentschik hferentschik changed the title Switch to a smaller base image for the jx image Switch to a smaller base image for the jx Jun 28, 2019
@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@hferentschik hferentschik changed the title Switch to a smaller base image for the jx Switch to a smaller base image for jx Mar 18, 2020
@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@hferentschik
Copy link
Author

/remove-lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement An enhancement of an existing feature lifecycle/rotten
Projects
None yet
Development

No branches or pull requests

2 participants