8000 chore(Dockerfiles): Refactor images to use ubuntu-slim by krancour · Pull Request #96 · deis/monitor · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(Dockerfiles): Refactor images to use ubuntu-slim #96

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

Merged
merged 3 commits into from
May 24, 2016
Merged

chore(Dockerfiles): Refactor images to use ubuntu-slim #96

merged 3 commits into from
May 24, 2016

Conversation

krancour
Copy link
Contributor
@krancour krancour commented May 23, 2016

Fixes #90

@krancour krancour added this to the v2.0-rc1 milestone May 23, 2016
@krancour krancour self-assigned this May 23, 2016
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @jchauncey and @sstarcher to be potential reviewers

@krancour krancour changed the title Image madness chore(Dockerfiles): Refactor images to use ubuntu-slim May 23, 2016
@sstarcher
Copy link
Contributor

influxdb version is not pinned at a specific version

&& . /etc/lsb-release \
&& echo "deb https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME} stable" | tee /etc/apt/sources.list.d/influxdb.list \
&& apt-get update \
&& apt-get install -y influxdb \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah im not sure i want to install influx like this. basically anytime this image builds we could get a newer version which isnt what we want here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the command 2 lines above pins it to a version, and then the above apt-get update adds the new repo metadata from the new source

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where is DISTRIB_ID and DISTRIB_CODENAME set?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arschles, @sstarcher and @jchauncey are correct. There isn't really anything pinning it to a specific version of influxdb here. What happens, as you've observed is that the official influxdb package repo gets added to apt-get's sources. We'll end up with whatever is in there.

For example:

root@e7909b499db6:/# apt-cache policy influxdb
influxdb:
  Installed: (none)
  Candidate: 0.13.0-1
  Version table:
     0.13.0-1 500
        500 https://repos.influxdata.com/ubuntu xenial/stable amd64 Packages
     0.10.0+dfsg1-1 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

While this may seem bad, it's no different from how the majority of all our packages are installed-- we get whatever is in the official repo(s).

How badly do we want to fix this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bad we cant ship this with that level of uncertainty. Since we arem oving to a deb based system we can just download the deb directly from them - https://influxdata.com/downloads/#influxdb

Telegraf has the same thing. https://influxdata.com/downloads/#telegraf

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with the latest, but I was just making sure it was the expected behavior. I tend to update my running influxdb prior to deis/monitor getting updated.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can do the latest which is fine but i dont want to have this thing potentially install a different version of influx just because we rebuild the image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can install specific debian versions sudo apt-get install influxdb=0.13.0-1

@krancour
Copy link
Contributor Author

After some offline discussion, I'm rescinding these LGTMs and will ask for a re-review shortly.

@krancour
Copy link
Contributor Author

I stead of adding sources to apt-get, I am now downloading version-specific debs, installing from those, then deleting them when done. This can be re-reviewed now.

@jchauncey
Copy link
Member

i didnt manually test this but looks good now

@arschles
Copy link
Member

Does this fix #90?

@krancour
Copy link
Contributor Author

#90 looks vague. Either it refers to the high severity issues with the official Grafana image we were previously deriving ours from and/or it refers to the fact that our Alpine-based images for telegraf and influxdb weren't being scanned at all.

In either of those cases, I feel this addressed #90. I've update the OP as such.

@krancour krancour merged commit 764a34d into deis:master May 24, 2016
@krancour krancour deleted the image-madness branch May 24, 2016 18:09
@jchauncey
Copy link
Member

Yeah for now
On May 24, 2016 12:29 PM, "Aaron Schlesinger" notifications@github.com
wrote:

Does this fix #90 #90?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#96 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0