<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vagrant Archives - Cube Websites</title>
	<atom:link href="https://cubewebsites.com/tag/vagrant/feed/" rel="self" type="application/rss+xml" />
	<link>https://cubewebsites.com/tag/vagrant/</link>
	<description>web design and development</description>
	<lastBuildDate>Tue, 25 Sep 2018 11:48:12 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://cubewebsites.com/wp-content/uploads/2019/04/cropped-favicon-32x32.png</url>
	<title>vagrant Archives - Cube Websites</title>
	<link>https://cubewebsites.com/tag/vagrant/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Quick Fix: MacOS Mojave Vagrant Error &#8211; tee: /etc/exports: Operation not permitted</title>
		<link>https://cubewebsites.com/software/quick-fix-macos-mojave-vagrant-error-tee-etc-exports-operation-not-permitted/</link>
					<comments>https://cubewebsites.com/software/quick-fix-macos-mojave-vagrant-error-tee-etc-exports-operation-not-permitted/#respond</comments>
		
		<dc:creator><![CDATA[Cube Websites]]></dc:creator>
		<pubDate>Tue, 25 Sep 2018 11:47:48 +0000</pubDate>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[macos]]></category>
		<category><![CDATA[vagrant]]></category>
		<category><![CDATA[virtualbox]]></category>
		<guid isPermaLink="false">https://cubewebsites.com/?p=526</guid>

					<description><![CDATA[<p>If you&#8217;ve updated to the newly released MacOS Mojave release then you might find the following issue when starting your vagrant box with NFS mounting: Preparing to edit /etc/exports. Administrator privileges will be required&#8230; Password: tee: /etc/exports: Operation not permitted tee: /etc/exports: Operation not permitted tee: /etc/exports: Operation not permitted You can quickly fix this [&#8230;]</p>
<p>The post <a href="https://cubewebsites.com/software/quick-fix-macos-mojave-vagrant-error-tee-etc-exports-operation-not-permitted/">Quick Fix: MacOS Mojave Vagrant Error &#8211; tee: /etc/exports: Operation not permitted</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you&#8217;ve updated to the newly released MacOS Mojave release then you might find the following issue when starting your vagrant box with NFS mounting:</p>
<p>Preparing to edit /etc/exports. Administrator privileges will be required&#8230;</p>
<pre>Password:
tee: /etc/exports: Operation not permitted
tee: /etc/exports: Operation not permitted
tee: /etc/exports: Operation not permitted</pre>
<p>You can quickly fix this issue by following the following steps:</p>
<ol>
<li>Open &#8220;System Preferences&#8221;</li>
<li>Go to &#8220;Security &amp; Privacy&#8221;</li>
<li>Click the &#8220;padlock&#8221; icon in the bottom-left corner where it says &#8220;Click the lock to make changes&#8221; &#8211; enter your password when prompted</li>
<li>On the list of permissions on the left, select &#8220;Full Disk Access&#8221;</li>
<li>Now, on the right-hand side, click the little &#8220;+&#8221; icon</li>
<li>This will open a browse window, use this to select your preferred Terminal e.g. &#8220;Applications &gt; iTerm&#8221; or &#8220;Applications &gt; Utilities &gt; Terminal&#8221;</li>
<li>If the selected Terminal is already open, you&#8217;ll be asked to Quit it &#8211; quit the application and restart it</li>
<li>When you restart the selected application, you may prompted if you&#8217;d like to allow the app to make changes to your computer &#8211; accept and enter your password if required</li>
<li>Try mounting your vagrant machine and now the above error should no longer appear!</li>
</ol>
<p>Note that this is a solution that I have tried and tested, but will be worth keeping an eye out for Vagrant/Virtualbox updates to see if they have an alternative solution.</p>
<p>The post <a href="https://cubewebsites.com/software/quick-fix-macos-mojave-vagrant-error-tee-etc-exports-operation-not-permitted/">Quick Fix: MacOS Mojave Vagrant Error &#8211; tee: /etc/exports: Operation not permitted</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://cubewebsites.com/software/quick-fix-macos-mojave-vagrant-error-tee-etc-exports-operation-not-permitted/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>FIX: Vagrant php-memcached error</title>
		<link>https://cubewebsites.com/development/fix-vagrant-php-memcached-error/</link>
					<comments>https://cubewebsites.com/development/fix-vagrant-php-memcached-error/#respond</comments>
		
		<dc:creator><![CDATA[Cube Websites]]></dc:creator>
		<pubDate>Thu, 14 Jan 2016 16:57:16 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[vagrant]]></category>
		<guid isPermaLink="false">http://www.cubewebsites.com/blog/?p=450</guid>

					<description><![CDATA[<p>I normally use PuPHPet to configure my Vagrant boxes. On my latest box using CentOS 5.6 the setup worked normally, but when trying to run my application I was getting the Class &#8216;Memcache&#8217; not found error. Usually this is a simple fix, just go in and type: sudo yum install -y php-memcached However, this time [&#8230;]</p>
<p>The post <a href="https://cubewebsites.com/development/fix-vagrant-php-memcached-error/">FIX: Vagrant php-memcached error</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>I normally use PuPHPet to configure my Vagrant boxes.<br />
On my latest box using CentOS 5.6 the setup worked normally, but when trying to run my application I was getting the Class &#8216;Memcache&#8217; not found error.</p>
<p>Usually this is a simple fix, just go in and type:</p>
<p><code>sudo yum install -y php-memcached</code></p>
<p>However, this time round the above was giving me the following error:</p>
<p><code>Transaction Check Error:<br />
  file /usr/lib64/libhashkit.so.2.0.0 conflicts between attempted installs of libmemcached-last-libs-1.0.18-2.el6.remi.x86_64 and libmemcached10-1.0.16-1.ius.centos6.x86_64<br />
  file /usr/lib64/libmemcached.so.11.0.0 conflicts between attempted installs of libmemcached-last-libs-1.0.18-2.el6.remi.x86_64 and libmemcached10-1.0.16-1.ius.centos6.x86_64<br />
  file /usr/lib64/libmemcachedutil.so.2.0.0 conflicts between attempted installs of libmemcached-last-libs-1.0.18-2.el6.remi.x86_64 and libmemcached10-1.0.16-1.ius.centos6.x86_64</code></p>
<p>After smashing my head against the desk a few times during numerous attempts at installing the module, reprovisioning the vagrant box and anything else I could think of doing to fix it, I tried something that hadn&#8217;t occurred to me before; to install the dependency it was complaining about first.</p>
<p>Using the following commands fixed my issue, and should also work for you:<br />
<code><br />
sudo yum install -y libmemcached-last<br />
sudo yum install -y php-memcached<br />
sudo service php-fpm restart<br />
</code></p>
<p>Hope this helps!</p>
<p>The post <a href="https://cubewebsites.com/development/fix-vagrant-php-memcached-error/">FIX: Vagrant php-memcached error</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://cubewebsites.com/development/fix-vagrant-php-memcached-error/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>FIX: Vagrant Pecl Error</title>
		<link>https://cubewebsites.com/development/tools/fix-vagrant-pecl-error/</link>
					<comments>https://cubewebsites.com/development/tools/fix-vagrant-pecl-error/#respond</comments>
		
		<dc:creator><![CDATA[Cube Websites]]></dc:creator>
		<pubDate>Wed, 05 Aug 2015 16:36:49 +0000</pubDate>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[puphpet]]></category>
		<category><![CDATA[vagrant]]></category>
		<guid isPermaLink="false">http://www.cubewebsites.com/blog/?p=445</guid>

					<description><![CDATA[<p>I just came across an issue where I updated my vagrant config and tried to provision the box, but it kept erroring out with the following error: ==&#62; default: Error: printf "\\n" &#124; pecl -d preferred_state=stable install pecl_http returned 1 instead of one of [0] ==&#62; default: Error: /Stage[main]/Puphpet_php/Puphpet::Php::Pecl[pecl_http]/Php::Pecl::Module[pecl_http]/Exec[pecl-pecl_http]/returns: change from notrun to 0 failed: [&#8230;]</p>
<p>The post <a href="https://cubewebsites.com/development/tools/fix-vagrant-pecl-error/">FIX: Vagrant Pecl Error</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>I just came across an issue where I updated my vagrant config and tried to provision the box, but it kept erroring out with the following error:</p>
<pre>==&gt; default: Error: printf "\\n" | pecl -d preferred_state=stable install pecl_http returned 1 instead of one of [0]
==&gt; default: Error: /Stage[main]/Puphpet_php/Puphpet::Php::Pecl[pecl_http]/Php::Pecl::Module[pecl_http]/Exec[pecl-pecl_http]/returns: change from notrun to 0 failed: printf "\\n" | pecl -d preferred_state=stable install pecl_http returned 1 instead of one of [0]
==&gt; default: Warning: /Stage[main]/Puphpet_php/Service[php5-fpm]: Skipping because of failed dependencies</pre>
<p>In order to fix this I logged into the server using SSH, and then manually ran the install pecl_http command that it was trying to run in the above error message.  In doing so I got a different error:</p>
<pre>$ sudo pecl -d preferred_state=stable install pecl_http</pre>
<pre>pecl/pecl_http requires package "pecl/raphf" (version &gt;= 1.1.0), installed version is 1.0.4
No valid packages found
install failed</pre>
<p>It turns out that a pecl dependency was out of date and so it couldn&#8217;t install the pecl_http package.  In order to fix it I just ran the pecl upgrade command.</p>
<pre>vagrant up
vagrant ssh
sudo pecl upgrade</pre>
<p>After running the above, I tried my vagrant provision again, and hey presto! Everything was working again as normal</p>
<p>The post <a href="https://cubewebsites.com/development/tools/fix-vagrant-pecl-error/">FIX: Vagrant Pecl Error</a> appeared first on <a href="https://cubewebsites.com">Cube Websites</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://cubewebsites.com/development/tools/fix-vagrant-pecl-error/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
