How to change the docker image installation directory?

With recent versions of Docker, you would set the value of the graph parameter to your custom path, in /etc/docker/daemon.json (according to https://docs.docker.com/v1.11/engine/reference/commandline/daemon/#daemon-configuration-file).
With older versions, you can change Docker's storage base directory (where container and images go) using the -goption when starting the Docker daemon. (check docker --help). You can have this setting applied automatically when Docker starts by adding it to /etc/default/docker

Comments

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream. Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl # will already be pre-configured export do = "--dry-run=client -o yaml" # k get pod x $do export now = "--force --grace-period 0" # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section . Question 1 | Contexts Task weight: 1% You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

亲身经历告诉你慎重去Meta WLB差的卷组

楼主终于要离职Meta了，终于离开了某卷组，原本以为自己是不怕累不怕加班的，心想如果多付出换来多回报也是值的。但事实给我上了一课，来跟大家分享一下不要选卷组的原因，以下都是楼主个人经历和想法，如有不同意见，轻喷。 1. 当卷组每个人都在疯狂contribute的时候，manager的期望会调整成组里的平均值，如果每个人都在疯狂加班，你也得被迫疯狂加班。我有时候甚至都怀疑有的人睡觉中途醒了是不是都会review个diff再继续睡。这种情况下，结果很可能是疯狂加班后也没有被recongnize也没有得到更多回报，简而言之就是rating未必更好，升职也不一定快。 2. 卷组的culture一言难尽。当大家都在疯狂赶工的时候，还顾得上考虑culture吗？当人在很忙很焦虑的时候，心态也不会很好。很多人在忙的时候说话就很冲，而且一不小心自己说错了什么也容易得罪人。Meta还有要peer feedback的习惯，有的时候感觉真的很憋屈... 3. 有的组太卷的原因是上面要的太多，而manager又很难或者不太会push back造成的。这种情况下，Eng加班是不情不愿的，疯狂赶工自然会牺牲质量，出了SEV以后，psc上面是要记一笔的。曾经见过某人疯狂赶project三四个月（上面期望的timeline不合理，但是push back无效），基本每天忙到凌晨12点到1点，但不小心搞出来一个SEV，最后psc给了个MA。大写的心疼... 4. 用lines of code 或者diff number作为一个重要的psc评判标准的组，要小心！个人认为这不是一个好事，有的project是需要investigate的，有的bug是需要时间才能查出来的。但是manager很难体谅，只会认为你能力低效率低（如果能体谅和理解，也不会把代码行数和diff 数量看那么重了是吧），这种情况下，很考验一个人在这个组待了多久和有多熟悉codebase里有多少坑（一般这么move fast的组，codebase很多都是shi山，暗坑无数），组员都很忙没有时间也没有义务告诉你哪里有坑，自己慢慢踩吧。现在就想到这么多吧，真心建议大家不要走我的老路选卷组了。珍爱生命，远离卷组！

Brain Dumps

Search This Blog