itamarst

35 ms·

331.
by itamarst 7y ago
Probably doesn't make sense to do that, no: https://news.mit.edu/2019/carbon-threshold-mass-extinction-0...
332.
by itamarst 7y ago
I ended up expanding this into a blog post covering not the linked article (though it shares some of the same flaws), but the official docs: https://pythonspeed.com/articles/official-docker-best-practi...
333.
A review of the official Dockerfile best practices: good, bad, and insecure(pythonspeed.com)
1 points by itamarst 7y ago|0 comments
334.
by itamarst 7y ago
Sometimes multi-stage builds are used to get build secrets into the build image. The final image just copies the resulting binaries over, and so you don't want to push the build image since you'd be leaking secrets. (I talk about
335.
by itamarst 7y ago
Yes! To be fair the official documentation Dockerfile best practices does mention this (although it also gives contradictory advice).
336.
by itamarst 7y ago
There are some people trying to build alternative toolchains for Docker builds that remove Dockerfiles altogether, e.g. https://buildpacks.io/ and (in a very different approach) Nix-based builds. My personal approach for Py
337.
by itamarst 7y ago
This isn't really about "getting the latest version", it's about "getting the latest security patches for a stable version." The presumption here is that you're running on a stable base image, Debian Stabl
338.
by itamarst 7y ago
The Python ones seem to be rebuilt much more frequently (last update was 10 days ago). This is perhaps because it depends on pip which has frequent releases.
339.
by itamarst 7y ago
As is the case with the Docker's best practices for Dockerfiles in the official documentation, they're leaving out some really important details. Specifically, they don't really express how Docker packaging is a process integ
340.
A thousand little details: why developing software for ops is so hard(pythonspeed.com)
4 points by itamarst 7y ago|0 comments
341.
The high cost of slow Docker builds(pythonspeed.com)
2 points by itamarst 7y ago|0 comments
342.
Connection refused? Docker networking and how it impacts your image(pythonspeed.com)
2 points by itamarst 7y ago|0 comments
343.
Watch me Dockerize a Python application in just 3 minutes (you can do it too!)(pythonspeed.com)
3 points by itamarst 7y ago|0 comments
344.
by itamarst 7y ago
1. Talk to former colleagues and friends; much more likely to hire you for shorter period since they already know you. 2. If you're willing to go for more like 32-30 hours, you can apply to normal jobs, then ask for shorter workweek on
345.
Faster Docker builds with pipenv, poetry, or pip-tools(pythonspeed.com)
2 points by itamarst 7y ago|0 comments
346.
Less capabilities, more security: minimizing privilege escalation in Docker(pythonspeed.com)
1 points by itamarst 7y ago|0 comments
347.
by itamarst 7y ago
Imagine you're a VC. Meal prep kit investments are hot. Your investors, the people giving you the money, come and say "how come you don't have the a meal prep kit startup in your portfolio?" Your choices are: 1. Don&#x27
348.
by itamarst 7y ago
1. It's much harder to negotiate early in your job. 2. Some people are less willing or able to negotiate for various reasons. Thus, while individuals can and should negotiate for themselves, negotiating for everyone is even better.
349.
by itamarst 7y ago
You don't have to wait for society to make this happen (and in fact waiting will fail you). This is something many programmers have negotiated on their own (e.g. https://codewithoutrules.com/2019/05/09/pa
350.
Docker build secrets, the sneaky (but secure!) way(pythonspeed.com)
1 points by itamarst 7y ago|0 comments
351.
by itamarst 7y ago
Non-privileged containers running as root are a definite security risk. Real world example: CVE from February 2019 which allowed escalation to root on host. It's preventable by (among other things) "a low privileged user inside th
352.
by itamarst 7y ago
Ah, neat, hadn't realized that was an actual Nix feature now. The post made it sound like this was just something they were writing for themselves.
353.
by itamarst 7y ago
This is why I have a caveat at the top of the article as well as right after the last example. This particular issue is fixable with `docker run --init`, so not strictly necessary to fix in images.
354.
by itamarst 7y ago
Like I said, it was very preliminary research... I reached the bit where pypi2nix did "nix-env -if https://github.com/garbas/pypi2nix/tarball/master" and wasn't super happy about the implicatio
355.
by itamarst 7y ago
Not an expert on Nix, but it's not so much that Nix has problems (though I'm sure it does, my initial research suggested it's not quite there yet for Python packages) but that there other things you need to get right. For exa
356.
by itamarst 7y ago
GitHub just bought Dependabot, so something like this is now available in beta and eventual general availability for all GitHub users.
357.
by itamarst 7y ago
This issue isn't Docker, Docker itself obviously can't deal with this. The issue is the examples and tutorial people provide on Docker packaging often don't talk about the requirements (pun intended) for reproducible builds a
358.
by itamarst 7y ago
Good point, will go fix that. My soon-to-be-ready attempt at a production-ready template ( https://pythonspeed.com/products/pythoncontainer/ ) covers the tradeoff between point releases vs. not-point-releases, and i
359.
Simple Dockerfile examples are often broken by default(pythonspeed.com)
461 points by itamarst 7y ago|157 comments
360.
by itamarst 7y ago
Negotiate a shorter workweek, e.g. 4 day workweek. Less exhaustion, and you can work on side projects on your remaining day.

More ›