<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Karim on Medium]]></title>
        <description><![CDATA[Stories by Karim on Medium]]></description>
        <link>https://medium.com/@abdulkarim_78118?source=rss-5243b0533b9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4pYVCjyeDyXL7tsnQtzjXQ.jpeg</url>
            <title>Stories by Karim on Medium</title>
            <link>https://medium.com/@abdulkarim_78118?source=rss-5243b0533b9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:57:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abdulkarim_78118/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Writing A Twitter Bot in Golang (Part 1)]]></title>
            <link>https://medium.com/@abdulkarim_78118/writing-a-twitter-bot-in-golang-part-i-bcc272565d58?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcc272565d58</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 11:57:28 GMT</pubDate>
            <atom:updated>2020-01-23T14:19:32.540Z</atom:updated>
            <content:encoded><![CDATA[<h4>One small bot for you but one large bot for mankind.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*PXQAI_4lPfLB-8laVIGDQg@2x.png" /><figcaption>credits: sketchappsources.com|golang.com</figcaption></figure><p>Golang has gained enough popularity in the past few years that it can no longer be avoided. To dive deep into the language I have started to build a simple twitter bot.</p><p>To start with, I decided to keep the problem statement fairly simple:</p><blockquote><strong>Search</strong> 5 recent tweets with tag #golang and <strong>Retweet</strong> them.</blockquote><p>It took me a couple of hours to hunt for the libraries and some example code to come up with code for this tutorial. You will take no more than 10 minutes if you follow the steps properly.</p><p>Before we get started we will need 3 things :</p><ul><li><a href="https://apps.twitter.com/app/new"><strong>Twitter API Keys</strong></a><strong>:</strong> Go to the <a href="https://apps.twitter.com/app/new">link</a> and follow the instructions. (You can also refer to this <a href="https://hackernoon.com/build-a-simple-twitter-bot-with-node-js-in-just-38-lines-of-code-ed92db9eb078">article</a> if you need help)</li><li><a href="https://golang.org/dl/"><strong>Golang</strong></a><strong>:</strong> If you don’t have golang installed already then <a href="https://golang.org/dl/">download it from their website</a>.</li><li><a href="https://github.com/dghubble/go-twitter#usage"><strong>go-twitter</strong></a><strong>: </strong>go-twitter is a Go client library for the <a href="https://dev.twitter.com/rest/public">Twitter API</a>. Check the <a href="https://github.com/dghubble/go-twitter#usage">usage</a> section or try the <a href="https://github.com/dghubble/go-twitter/blob/master/examples">examples</a> to see how to access the Twitter API.</li></ul><h3>Setup Workspace</h3><p>Start with creating a directory and the files that are needed. Also install the dependencies for the project</p><pre>mkdir -p ~/tweetbot<br>cd ~/tweetbot<br>touch bot.go<br>go get -u </pre><h3>Test API keys</h3><p>Before getting into the implementation of the logic for search and retweet let’s quickly test our twitter API keys. Make a file name login_test.go</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ebc043a3e7ea4a4296fddd4bfa304b44/href">https://medium.com/media/ebc043a3e7ea4a4296fddd4bfa304b44/href</a></iframe><ol><li><em>import</em> required packages.</li><li>Add twitter API secrets. These keys and tokens are sensitive and you should not share it with anybody.</li><li>Initialize twitter client</li><li>verifyParams variable is required for client.Account.VerifyCredentials function.</li><li>The client.Accounts.VerifyCredentials returns user information.</li><li>Print the user’s twitter handle with user.ScreenName.</li></ol><pre>$ go run login_test.go<br>User&#39;s Name:abdulkarim_me</pre><h3>Build the Bot</h3><p>Our problem statements has 2 parts</p><ul><li><strong>Search</strong> 5 recent tweets with tag #golang</li><li><strong>Retweet</strong> them.</li></ul><h4>Search</h4><p>For search, we will use Tweets() function which returns a collection of Tweets matching a search query. First, build the searchParams with required values and pass it to the Search function. (Only Query is a required field here, rest can be omitted).</p><pre>...<br>// Search tweets to retweet<br> searchParams := &amp;twitter.SearchTweetParams{<br>  Query:      &quot;#golang&quot;,<br>  Count:      5,<br>  ResultType: &quot;recent&quot;,<br>  Lang:       &quot;en&quot;,<br> }</pre><pre>searchResult, _, _ := client.Search.Tweets(searchParams)<br>...</pre><h4>Retweet</h4><p>Iterate over the searchResult and retweet all the tweets for which we will need the ID of the tweets. Retweetretweets the Tweet with the given id and returns the original Tweet with embedded retweet details. Requires a user auth context.</p><pre>...</pre><pre>// Iterate an retweet<br>for _, tweet := range searchResult.Statuses {<br>  tweet_id := tweet.ID<br>  client.Statuses.Retweet(tweet_id, &amp;twitter.StatusRetweetParams{})</pre><pre>fmt.Printf(&quot;RETWEETED: %+v\n&quot;, tweet.Text)<br> }<br>...</pre><p>Voila! That’s it and you have your twitter bot ready that will retweet #golang tweets (or anything you want) for you. The complete code looks like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e5065d496b95660df7173c90b6528655/href">https://medium.com/media/e5065d496b95660df7173c90b6528655/href</a></iframe><pre>$ go run bot.go</pre><pre>RETWEETED: RT <a href="http://twitter.com/dgryski">@dgryski</a>: The 10 minutes where you test your #golang replacement of a #perl service:<br>(Y axis is in ms) <a href="https://t.co/SB9D2am3aI">https://t.co/SB9D2am3aI</a><br>RETWEETED: RT <a href="http://twitter.com/kdnuggets">@kdnuggets</a>: Understanding #Tensorflow using #GoLang <a href="https://t.co/J1dsjZzPKk">https://t.co/J1dsjZzPKk</a> <a href="https://t.co/4Et9pZIiio">https://t.co/4Et9pZIiio</a><br>RETWEETED: RT <a href="http://twitter.com/cjrolo">@cjrolo</a>: Never imagined that it would be possible that <a href="http://twitter.com/code">@code</a> is replacing all my IDEs so fast. #golang #python #java even #markdown and…<br>RETWEETED: RT <a href="http://twitter.com/cjrolo">@cjrolo</a>: Never imagined that it would be possible that <a href="http://twitter.com/code">@code</a> is replacing all my IDEs so fast. #golang #python #java even #markdown and…<br>RETWEETED: Never imagined that it would be possible that <a href="http://twitter.com/code">@code</a> is replacing all my IDEs so fast. #golang #python #java even #markdown and LaTeX...</pre><p>Our bot is very primitive and will need a lot more attention in the coming days. Here are some of the ToDo’s that I have in mind</p><ul><li>Parameterize the bot. (#golang or #ruby should be passed as an argument)</li><li>Greet your followers</li><li>Favourite if somebody retweets your tweet</li><li>Follow Bot. (If follow &lt;-&gt; You follow)</li><li>Dockerize the bot so it can be executed on any machine.</li><li>Setup a cronjob</li></ul><h4>❤ If this post was helpful, please hit the little green heart!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcc272565d58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DRY — an Alternate Command Line Tool for Docker]]></title>
            <link>https://medium.com/hackernoon/docker-cli-alternative-dry-5e0b0839b3b8?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e0b0839b3b8</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Wed, 31 May 2017 15:26:41 GMT</pubDate>
            <atom:updated>2019-04-25T09:28:42.524Z</atom:updated>
            <content:encoded><![CDATA[<h4>Comparison of <strong>dry versus docker cli.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bb2Pir68zR0TXrk9lZQvcA.png" /></figure><p><a href="https://moncho.github.io/dry/">Dry</a> is a terminal application to manage <a href="https://hackernoon.com/tagged/docker">Docker</a> containers and images. It aims to be an alternative to the official Docker CLI when it is needed to repeatedly execute commands on existing containers and images, and also as a tool to monitor Docker containers from a terminal. You can think of Dry as htop for containers.</p><h4>Installation</h4><pre>## LINUX<br>$ curl -sSf https://moncho.github.io/dry/dryup.sh | sudo sh<br>$ sudo chmod 755 /usr/local/bin/dry </pre><pre>## MAC<br>brew tap moncho/dry<br>brew install dry</pre><h4>Usage</h4><pre>$ dry</pre><p>This will open up a prompt loaded with all the useful information about the docker daemon and the containers that are running. It can connect to local or remote docker host. In this example we are connected to local daemon (unix:///var/run/docker.sock).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSBopNXFt-soJvCgbg3X8w.png" /><figcaption>top: dry | bottom: docker ps</figcaption></figure><p>This image shows a comparison between docker ps and dry. The dry experience is definitely much better than the default docker cli.</p><h4>monitor</h4><p>You can enter the monitor mode in dry by pressing m key. This is equivalent to docker stats command. Let’s see how the monitoring compares between the two</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kLDok1NnNDpqocqvIBhq7Q.png" /><figcaption>top: dry | bottom: docker stats</figcaption></figure><p>Both the <a href="https://hackernoon.com/tagged/tools">tools</a> provide similar metrics but again dry has more verbose and colored output. It also has an additional NAME column which comes handy at times when you have many containers you are not a memory champion.</p><h4>containers</h4><p>If you select a container from the main menu you get a list of operations that can be performed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgO48e31sJQMW7zbWFnsog.png" /><figcaption>` dry: containers</figcaption></figure><p>You can view logs, inspect, kill and do a bunch of other things to the container. The Stats+Top is a useful feature that shows the resource utilization and output of top from the container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O16kRkvyGbrzrK4MGFhjbQ.png" /><figcaption>dry: Stats + Top</figcaption></figure><p>The docker cli flow would be to first fetch the container id from docker ps and then execute top interactively inside the container docker exec -it &lt;container_id&gt; top.</p><h4>images</h4><p>You can operate on images by pressing 2 inside the main menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3fAt_Vrth96Q0j8zK1MZw.png" /><figcaption>dry: images</figcaption></figure><p>If you want to remove an image simply select it from the menu and press Ctrl + E. For force removal you must use Ctrl + F.</p><h4>help</h4><p>To get help on dry commands you can start dry and press H key or visit their <a href="https://github.com/moncho/dry">github page</a>.</p><p>Dry may not add a lot of value for everyone but it is definitely some sugar on top of vanilla docker cli. I use this tool a lot and would recommend others to give it a try.</p><h4>❤ If this post was helpful, please hit the little green heart!</h4><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e0b0839b3b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/docker-cli-alternative-dry-5e0b0839b3b8">DRY — an Alternate Command Line Tool for Docker</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cache-Mirror Dockerhub For Speed]]></title>
            <link>https://medium.com/@abdulkarim_78118/mirror-cache-dockerhub-locally-for-speed-f4eebd21a5ca?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4eebd21a5ca</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[caching]]></category>
            <category><![CDATA[proxy]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Mon, 29 May 2017 18:39:10 GMT</pubDate>
            <atom:updated>2020-01-28T14:18:48.452Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*dCsPYlrz9CKUK6akoxycyA.png" /><figcaption><a href="https://www.docker.com/sites/default/files/oyster-registry-3.png">https://www.docker.com/sites/default/files/oyster-registry-3.png</a></figcaption></figure><p>If you have a bunch of Docker instances (physical or VM) running, each time one of them pulls an image that is not present on the host, it will fetch it from the internet (<a href="https://hackernoon.com/tagged/dockerhub">DockerHub</a>). By caching these images, you can keep the traffic within your local <a href="https://hackernoon.com/tagged/network">network</a> and avoid <em>egress</em> bandwidth usage. In this article, we will see how to setup <a href="https://docs.docker.com/registry/recipes/mirror/">docker registry as a pull-through cache</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*KN-t9g15tYGFzYsM_34Bzw.png" /></figure><h3>How does it work?</h3><p>Just like any other caching works, the first time any docker client tries to pull an image it will fetch the image from Dockerhub and also store a copy on the filesystem. On any subsequent request, you get served from the local registry rather than DockerHub. It is smart enough to detect any changes to the image upstream and update the image before serving it to the client.</p><p>Let’s try this with an example. I have <a href="https://github.com/techmaniack/docker-local-cache">written a small compose file</a> that you can run locally to test this. It requires running one container and updating the docker daemon settings.</p><p><strong>Step 1</strong>: Run docker registry</p><pre>$ git clone https://github.com/techmaniack/docker-local-cache.git<br>$ cd docker-local-cache<br>$ docker-compose up -d</pre><p>Verify that the container is up and listening on port 5000</p><pre>$ curl -I localhost:5000/                                                                    [23:40:30]<br>HTTP/1.1 200 OK<br>Cache-Control: no-cache<br>Date: Mon, 29 May 2017 18:10:33 GMT<br>Content-Type: text/plain; charset=utf-8</pre><p>[The images will be cached in docker-local-cache/.data/ directory.]</p><p><strong>Step 2</strong>: Update the docker daemon configuration</p><p>On OSX you can open docker preferences and under <em>Daemon &gt; Registry Mirrors</em> add ‘http://localhost:5000’ and restart docker service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*GTlTXS5M79zUV6sPraaPhw.png" /></figure><p>That’s it! You have successfully installed and configured the <a href="https://docs.docker.com/registry/recipes/mirror/">docker registry as a pull-through cache</a>.</p><p>Let’s quickly see it in action.</p><pre>$ time docker pull mongo<br>Using default tag: latest<br>latest: Pulling from library/mongo<br>...<br>Status: Downloaded newer image for mongo:latest<br>docker pull mongo  0.17s user 0.07s system 0% cpu 1:11.08 total<br><br>$ docker rmi mongo<br>Untagged: mongo:latest<br>Untagged: mongo@sha256:c4bc4644b967a4b58022a79cf5c9afcd25ed08180c958a74df57b7753cfc8649<br>...<br>Deleted: sha256:5d924e3b1efdcda770bc33e6d7563f5ca2411dcc6b7368c8a30356bed474ae5a<br><br>$ time docker pull mongo<br>Using default tag: latest<br>latest: Pulling from library/mongo<br>...<br>Status: Downloaded newer image for mongo:latest<br>docker pull mongo  0.13s user 0.05s system 0% cpu 19.296 total</pre><p>As you can see the first docker pull took <strong>71 seconds</strong> while the second pull is completed in <strong>19 seconds</strong>. #somuchwin</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4eebd21a5ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker compose unusual behaviour]]></title>
            <link>https://medium.com/@abdulkarim_78118/docker-compose-unusual-behaviour-bbb4025e144f?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbb4025e144f</guid>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[opinion]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sat, 27 May 2017 14:57:03 GMT</pubDate>
            <atom:updated>2017-05-27T14:57:03.228Z</atom:updated>
            <content:encoded><![CDATA[<p>Compose is a powerful tool that takes away a lot of pain from managing multiple containers on your local machine.</p><h4>docker-compose run — rm</h4><p>Just like docker run --rm &lt;IMAGE&gt; you would expect compose to cleanup the resources post operation completion but it cleans only the target container and does not terminate the linked containers.</p><p>An example will make it clear. Consider this composition</p><pre>version: &quot;3&quot;<br>services:<br>  nginx:<br>    image: nginx<br>  web:<br>    image: php<br>    depends_on:<br>      - db<br>  db:<br>    image: redis</pre><p>Now if you try to run a one time command in the web container you can see the web container is removed but the db still remains. You have to manually remove the linked containers with docker-compose down.</p><pre>$ docker-compose run --rm web bash                                                                        <br>Creating network &quot;dockercomposerm_default&quot; with the default driver<br>Creating dockercomposerm_db_1 ...<br>Creating dockercomposerm_db_1 ... done<br>root@26ea74ee26ca:/# exit<br>exit</pre><pre>$ docker ps -a                                                                                            [20:11:23]<br>CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES<br>a35c9e2da7a8        redis               &quot;docker-entrypoint...&quot;   11 seconds ago      Up 10 seconds       6379/tcp            dockercomposerm_db_1</pre><p>In my opinion the --rm tag should cleanup all linked resources as well.</p><p>This issue has been <a href="https://github.com/docker/compose/issues/2791">discussed on Github</a> and the developers don’t plan to fix this at the moment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbb4025e144f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Github Project from Your Terminal]]></title>
            <link>https://medium.com/@abdulkarim_78118/open-github-page-from-your-terminal-42d709b66f87?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/42d709b66f87</guid>
            <category><![CDATA[zsh]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Fri, 26 May 2017 16:29:43 GMT</pubDate>
            <atom:updated>2017-06-12T23:50:03.607Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://github.com/paulirish/git-open">git-open</a> is a script that allows you to open the Github project straight from your terminal. It is a simple feature but can save you a lot of time. You can see it in action here</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*dJ9JpS9hn8tMl4krlbX1Tg.gif" /><figcaption><a href="https://github.com/paulirish/git-open">https://github.com/paulirish/git-open</a></figcaption></figure><p>If you are using zsh then installating git-open is very simple.</p><ol><li>cd ~/.oh-my-zsh/custom/plugins</li><li>git clone git@github.com:paulirish/git-open.git</li><li>Add git-open to your plugin list - edit ~/.zshrc and change plugins=(...) to plugins=(... git-open)</li><li>source ~/.zshrc</li></ol><p>You can find other installation methods <a href="https://github.com/paulirish/git-open">here</a>.</p><h4>❤ If this post was helpful, please hit the little green heart!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42d709b66f87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Solved] Vagrant openssl issue]]></title>
            <link>https://medium.com/@abdulkarim_78118/solved-vagrant-openssl-issue-b5edd25873b7?source=rss-5243b0533b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5edd25873b7</guid>
            <category><![CDATA[vagrant]]></category>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[coreos]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Mon, 22 May 2017 13:59:58 GMT</pubDate>
            <atom:updated>2017-05-22T13:59:58.227Z</atom:updated>
            <content:encoded><![CDATA[<p>I was trying to setup coreOS cluster locally using the official vagrant files provided by CoreOS team but `vagrant up` was throwing this nasty error:</p><pre>WARNING: can&#39;t open config file: /vagrant-substrate/staging/embedded/ssl/openssl.cnf<br>Generating RSA private key, 2048 bit long modulus<br>..............................................................................................................+++<br>...............................................................................................+++<br>e is 65537 (0x10001)<br>WARNING: can&#39;t open config file: /vagrant-substrate/staging/embedded/ssl/openssl.cnf<br>Unable to load config info from /vagrant-substrate/staging/embedded/ssl/openssl.cnf<br><strong>failed generating SSL artifacts</strong></pre><p>After doing some google I found the soultion</p><blockquote>sudo ln -sf /usr/local/bin/openssl /opt/vagrant/embedded/bin/openssl</blockquote><p><a href="https://opensource.ncsa.illinois.edu/confluence/pages/viewpage.action?pageId=105251761">Reference</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5edd25873b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>