Docker. How to get bash\ssh inside running container (run -d)?

source: http://askubuntu.com/a/507009/89694

$ sudo docker attach 665b4a1e17b6 #by ID
or
$ sudo docker attach loving_heisenberg #by Name
$ root@665b4a1e17b6:/# 

UPDATE: (docker >= 1.3) Thanks to WiR3D user who suggested another way to get container’s shell. If we use attach we can use only one instance of shell. So if we want open new terminal with new instance of container’s shell, we just need run the following:

$ sudo docker exec -i -t 665b4a1e17b6 bash #by ID
or
$ sudo docker exec -i -t loving_heisenberg bash #by Name
$ root@665b4a1e17b6:/#

 

 

Ten Quick Tips to Improve Your Chef Workflow – ChefConf 2015

Checkout this youtube (just below 11minutes): Ten Quick Tips to Improve Your Chef Workflow – ChefConf 2015

1. Chef on a Windows workstation.
2. Shared ServerSpec Helper files.
3. https://docs.chef.io/dsl_recipe.html#shell-out
4. use screen recording software.
5. use pre-baked VMs or Containers
6. troubleshoot with Pry.
7. use run_state to store data, available later in the chef run.
8. coerce everthing instead of checking for .nil?
9. use a good text editor.
X. write stuff done, then add them to SCM.

your-dns-needs-immediate-attention

For everybody who has an issue with the text: your-dns-needs-immediate-attention
for example:

ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ECONNREFUSED: Connection refused - connect(2) for "your-dns-needs-immediate-attention.dev" port 443 (https://your-dns-needs-immediate-attention.dev)

This is problably because the .dev and .local are now valid top level extensions.

i had to solve this, add “search home.local” to “/etc/resolv.conf”
(actually added this to “/etc/resolvconf/resolv.conf.d/head”)