soulshake / clink Goto Github PK

Run a container as easily as any other command

Shell 100.00%

clink's Introduction

Hi there 👋

🔭 I work on EphemeraSearch
😍 I have an unhealthy obsession with GNU Make
🧬 I’m currently learning genomics at Quantgene
👯 I’m looking to collaborate on EphemeraSearch
🤔 I’m looking for help with German
💬 Ask me about old postcards, genealogy, hydroponics, lucid dreaming
📫 How to reach me: @s0ulshake
😄 Pronouns: she/they
⚡ Fun fact: I <3 dumpsters

For details, run:

curl cv.soulshake.net

Languages this week

Python       8 hrs 36 mins   ████████████░░░░░░░░░░░░░   47.45 %
Terraform    6 hrs 9 mins    ████████▒░░░░░░░░░░░░░░░░   33.99 %
Other        1 hr 22 mins    ██░░░░░░░░░░░░░░░░░░░░░░░   07.55 %
JavaScript   1 hr 11 mins    █▓░░░░░░░░░░░░░░░░░░░░░░░   06.59 %
YAML         24 mins         ▓░░░░░░░░░░░░░░░░░░░░░░░░   02.26 %

Languages all time

clink's People

Contributors

Stargazers

Watchers

Forkers

jpetazzo lindt afcarl cybernetics

clink's Issues

When sourced within a container, command_not_found_handle causes infinite loop

I have PrtSc set up in my i3 profile to a script that runs a command using the AWS CLI: bindsym Print exec "~/bin/screenshot.sh"

When I run "~/bin/screenshot.sh" directly it works as expected, but when it's executed via the i3 bindsym, it spawns more and more aws processes until I kill the container.

This is what I think is happening:
If a user runs a container-command from $HOME, their homedir is mounted in the container. When a container's entrypoint isn't fully qualified, this can result in the aliased version of the command preceding the "real" command in the container-user's $PATH, resulting in an infinite loop.

support for private registries

currently just official images seem to be supported. public and private registry

ubuntu

works

but

foo/ubuntu

does not work, even if it would exist.

env breaks for multi line environments

i've a multi line ENV called

BASH_FUNC=() {  . /usr/share/foo.sh
}

my container will then be called with --env "}"

probably dangerous?

alpine not working

could not describe any further now. but want to keep the other issue clean from this discussion here.
even "ubuntu" is not working anymore on master.

will investigate on this, once I'm able to run "ubuntu" again.

expectation:

> alpine /bin/sh

should open a docker container based on alpine.

IP traffic from Seattle to Baltimore goes through Paris; affects LISA Docker training

From @jpetazzo on November 9, 2014 23:16

Hi friends,

The latency between the conference WiFi and the Gandi VMs in Baltimore
is very high (>250ms RTT). According to MTR, the traffic gets routed
through Paris. Here's a MTR trace from the local network a VM in Baltimore:

 Host                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.32.2                           0.0%    10    2.0   1.4   1.0   2.0   0.0
 2. s4-0-0-10--0.gw02.sttl.eli.net         0.0%     9    2.0   6.4   1.9  32.8  10.3
 3. tg9-2.cr01.sttlwatw.integra.net        0.0%     9   11.2   7.3   4.3  11.2   2.4
 4. 209.63.101.2                           0.0%     9    4.7   3.5   2.5   4.7   0.6
 5. tg0-0-0-0.br02.nycmny83.integra.net    0.0%     9   71.0  74.3  70.0 100.6   9.9
 6. 80.249.209.244                         0.0%     9  164.3 165.3 164.3 167.2   0.8
 7. xe0-0-2-3.c2-4-d.core4-d.paris.gandi.  0.0%     9  265.7 265.8 264.3 268.5   1.1
 8. xe2-1-24-vcore1-dc1.balt.gandi.net     0.0%     9  267.7 291.1 266.6 410.9  48.7
 9. 4xe-pc400.vdist1-dc1.balt.gandi.net    0.0%     9  264.8 264.4 263.5 264.9   0.0
10. xvm-106-170.dc1.ghst.net               0.0%     9  264.7 264.4 263.9 264.8   0.0

This is really bad because it gives the impression that the VMs are slow. 🐌

Can we do anything about it?

Note: the training is Wednesday. So we don't need to wake up anyone right now,
but if this is not fixed by Tuesday, we will switch to Amazon us-west-2 to
minimize the risks. Here is a MTR to a VM in us-west-2 on EC2:

 1. 192.168.32.2                           0.0%     6    1.3   1.1   0.8   1.7   0.0
 2. s4-0-0-10--0.gw02.sttl.eli.net         0.0%     6    2.0   2.1   1.8   2.3   0.0
 3. tg9-2.cr02.sttlwatw.integra.net        0.0%     6    2.8   7.3   2.8  10.3   2.8
 4. 209.63.101.6                           0.0%     6    2.5   2.5   2.1   3.6   0.4
 5. six01-sea4.amazon.com                  0.0%     6    2.6   2.7   2.5   2.9   0.0
 6. 205.251.225.166                        0.0%     6    1.9   2.0   1.8   2.0   0.0
 7. 205.251.232.79                         0.0%     6    8.7   8.6   8.0   9.9   0.6
 8. 205.251.232.215                        0.0%     6    9.8  10.8   9.7  13.8   1.5
 9. 205.251.232.61                         0.0%     6    9.8   9.1   8.2   9.8   0.0
10. ???
11. ???
12. ???
13. ec2-54-69-114-186.us-west-2.compute.a  0.0%     5    8.8   9.4   8.8   9.9   0.0

Let us know if there is anything we can do here (traceroutes or anything else) to help!

Thanks. 🐳

Copied from original issue: soulshake/docker-training#11

soulshake / clink Goto Github PK

clink's Introduction

Hi there 👋

Languages this week

Languages all time

clink's People

Contributors

Stargazers

Watchers

Forkers

clink's Issues

When sourced within a container, command_not_found_handle causes infinite loop

support for private registries

env breaks for multi line environments

alpine not working

IP traffic from Seattle to Baltimore goes through Paris; affects LISA Docker training

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent