Thanks for the reply Sam!
I think I learned another thing today, don't just trust 'docker run
hello-world' to verify your docker configuration ;) In the end it was a
network problem with Docker on my side and strange enough a reboot solved
it.
The image is still building but I'll keep this list up
On Tue, Nov 19, 2019 at 2:13 PM Roy Lenferink wrote:
>
> I just tried the Docker instructions, however the rake docker:update
> command is failing for me with the error shown below. Am I maybe missing
> something?
[snip]
> Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
> Tem
For the /srv checkouts, if you make them volumes, you can override that at
runtime to use a bound directory instead of a generic Docker volume (which
itself just goes in Docker’s data directory otherwise). Using a volume is
important regardless for file system performance on that data.
As for keep
On Tue, 19 Nov 2019 at 17:49, Sam Ruby wrote:
> On Tue, Nov 19, 2019 at 9:15 AM sebb wrote:
> >
> > On Tue, 19 Nov 2019 at 13:34, Sam Ruby wrote:
> >
> > > On Tue, Nov 19, 2019 at 8:17 AM sebb wrote:
> > > >
> > > > On Tue, 19 Nov 2019 at 12:26, sebb wrote:
> > > >
> > > > > docker:update had
I just tried the Docker instructions, however the rake docker:update
command is failing for me with the error shown below. Am I maybe missing
something?
I am on CentOS 8.0.1905 with Docker version 19.03.5, build 633a0ea.
I also tested using podman with podman-compose (with alias docker='podman'
e
On Tue, Nov 19, 2019 at 9:15 AM sebb wrote:
>
> On Tue, 19 Nov 2019 at 13:34, Sam Ruby wrote:
>
> > On Tue, Nov 19, 2019 at 8:17 AM sebb wrote:
> > >
> > > On Tue, 19 Nov 2019 at 12:26, sebb wrote:
> > >
> > > > docker:update had issues pulling down various svn repos, e.g.
> > > >
> > > > svn:
On Tue, 19 Nov 2019 at 13:34, Sam Ruby wrote:
> On Tue, Nov 19, 2019 at 8:17 AM sebb wrote:
> >
> > On Tue, 19 Nov 2019 at 12:26, sebb wrote:
> >
> > > docker:update had issues pulling down various svn repos, e.g.
> > >
> > > svn: E170013: Unable to connect to a repository at URL ...
> > > svn
On Tue, Nov 19, 2019 at 8:17 AM sebb wrote:
>
> On Tue, 19 Nov 2019 at 12:26, sebb wrote:
>
> > docker:update had issues pulling down various svn repos, e.g.
> >
> > svn: E170013: Unable to connect to a repository at URL ...
> > svn: E125009: Invalid config: unable to load certificate file
> > '
On Tue, 19 Nov 2019 at 12:26, sebb wrote:
> docker:update had issues pulling down various svn repos, e.g.
>
> svn: E170013: Unable to connect to a repository at URL ...
> svn: E125009: Invalid config: unable to load certificate file
> '/Users/sebb/.subversion/Thawte_Premium_Server_CA.pem'
>
> I
docker:update had issues pulling down various svn repos, e.g.
svn: E170013: Unable to connect to a repository at URL ...
svn: E125009: Invalid config: unable to load certificate file
'/Users/sebb/.subversion/Thawte_Premium_Server_CA.pem'
I was able to remove the Invalid config error by changing
On Sat, Oct 19, 2019 at 12:43 AM Dave Fisher wrote:
>
> Maybe a docker image is the way to go. I’ll test it if you point it out.
Beta testers wanted: https://github.com/apache/whimsy/blob/master/DOCKER.md
- Sam Ruby
On Sat, Oct 19, 2019 at 6:39 AM Sam Ruby wrote:
>
> On Sat, Oct 19, 2019 at 12:43 AM Dave Fisher wrote:
> >
> > Maybe a docker image is the way to go. I’ll test it if you point it out.
>
> A docker image is VERY appealing. There are things that don't work
> and/or are hard to do on Mac (for exam
On Sun, Oct 20, 2019 at 9:23 AM Sam Ruby wrote:
>
> On Sat, Oct 19, 2019 at 7:19 PM Sam Ruby wrote:
> >
> > P.S. Not a priority for me at this next week, but it occurs to me that
> > newer versions of MAC OS/X may have newer versions of Apache HTTPD, so
> > we may no longer need the brew version
On Sat, Oct 19, 2019 at 7:19 PM Sam Ruby wrote:
>
> P.S. Not a priority for me at this next week, but it occurs to me that
> newer versions of MAC OS/X may have newer versions of Apache HTTPD, so
> we may no longer need the brew version of Apache HTTPD, which these
> days require manual patches to
On Sat, Oct 19, 2019 at 12:05 AM Sam Ruby wrote:
>
> With the latest update (Catalina):
>
> $ sudo mkdir /srv
> mkdir: /srv: Read-only file system
>
> Previously, whimsy tools were set up to determine file names based on
> a ~/.whimsy config file. Over time, much of this has changed to
> presume
On Sat, 19 Oct 2019 at 12:01, Sam Ruby wrote:
>
> On Sat, Oct 19, 2019 at 5:00 AM sebb wrote:
> >
> > Also /srv is actually a link to /x1/srv on Ubuntu, so potentially it
> > could be changed in stages?
>
> There is no /srv directory. There is no /x1 directory. And neither
> can be created. Th
On Sat, Oct 19, 2019 at 5:00 AM sebb wrote:
>
> Also /srv is actually a link to /x1/srv on Ubuntu, so potentially it
> could be changed in stages?
There is no /srv directory. There is no /x1 directory. And neither
can be created. There are two volumes. The root volume is read only.
/System/Vo
On Sat, Oct 19, 2019 at 12:43 AM Dave Fisher wrote:
>
> Maybe a docker image is the way to go. I’ll test it if you point it out.
A docker image is VERY appealing. There are things that don't work
and/or are hard to do on Mac (for example, setting up Apache httpd
with LDAP enabled as brew no long
Does /srv contain anything?
Or is it an empty directory like /home?
If it's empty, then I found out that it's possible to mount a container over it.
S.
On Sat, 19 Oct 2019 at 05:44, Dave Fisher wrote:
>
> Or is chmod your friend?
>
> Sent from my iPhone
>
> > On Oct 18, 2019, at 9:05 PM, Sam R
Also /srv is actually a link to /x1/srv on Ubuntu, so potentially it
could be changed in stages?
On Sat, 19 Oct 2019 at 09:53, sebb wrote:
>
> Does /srv contain anything?
>
> Or is it an empty directory like /home?
>
> If it's empty, then I found out that it's possible to mount a container over
Or is chmod your friend?
Sent from my iPhone
> On Oct 18, 2019, at 9:05 PM, Sam Ruby wrote:
>
> With the latest update (Catalina):
>
> $ sudo mkdir /srv
> mkdir: /srv: Read-only file system
>
> Previously, whimsy tools were set up to determine file names based on
> a ~/.whimsy config file. O
Catalina did some annoying things. For me emacs was gone as Apple doesn’t like
gpl3.
There is more security on directories.
Maybe a docker image is the way to go. I’ll test it if you point it out.
Sent from my iPhone
> On Oct 18, 2019, at 9:05 PM, Sam Ruby wrote:
>
> With the latest update (
With the latest update (Catalina):
$ sudo mkdir /srv
mkdir: /srv: Read-only file system
Previously, whimsy tools were set up to determine file names based on
a ~/.whimsy config file. Over time, much of this has changed to
presume /srv. Most problematic:
$LOAD_PATH.unshift '/srv/whimsy/lib'
No
23 matches
Mail list logo
