> I have a very simple container that I use for building Arch packages, just
> added it to the Docker Hub so others can use it:
> https://registry.hub.docker.com/u/tazjin/arch-pkgbuild/
>
I just want to share with you my Docker image as well, which adds a couple of
features to Vincent's, which a
>
> Very nice. I can definitely use it as a base for my building. One
> thing though, I can't seem to find any pre-built 32-bit image though.
You might have to bootstrap an Arch base container with 32-bit yourself.
Should be doable by running the mkimage-arch script in a 32-bit VM:
https://gith
On Thu, Sep 04, 2014 at 09:11:17PM +0200, Vincent Ambo wrote:
> I have a very simple container that I use for building Arch
> packages, just added it to the Docker Hub so others can use it:
> https://registry.hub.docker.com/u/tazjin/arch-pkgbuild/
>
> It's basically an Arch container that gets upd
On 4 Sep 2014 20:00, "Neven Sajko" wrote:
>
> Magnus, did you run that lxc-create with root rights?
No, I did not. I thought that might be case, but there were no explicit
mentions of this and all the usual visual cues in the docs were missing (no
calls to 'sudo' and the prompt was $).
But in my
On Thu, Sep 04, 2014 at 07:24:36AM +0200, Magnus Therning wrote:
> As always complex doesn't automatically translate to complicated ;)
>
> In this particular case I had no issues with following the
> instructions I found on docker. While when spending the same amount
> of time on getting lxc to w
On Wed, Sep 03, 2014 at 10:26:11PM +0200, Magnus Therning wrote:
> Oki, I've never looked at lxc, I was under the impression that docker
> used to build on lxc in the past. Is that not true any longer?
It was true, yes, but I don't think it is now. Although, I can't find a link
ATM.
> Is there a
I have a very simple container that I use for building Arch packages, just
added it to the Docker Hub so others can use it:
https://registry.hub.docker.com/u/tazjin/arch-pkgbuild/
It's basically an Arch container that gets updated at image create time and
has base-devel installed. When running the
Magnus, did you run that lxc-create with root rights?
On 4 September 2014 07:24, Magnus Therning wrote:
> On Wed, Sep 03, 2014 at 12:36:23PM -0400, Leonid Isaev wrote:
> > On Wed, Sep 03, 2014 at 09:04:37AM +0200, Magnus Therning wrote:
> > > For various reasons I'm looking into not using `make
On Wed, Sep 03, 2014 at 12:36:23PM -0400, Leonid Isaev wrote:
> On Wed, Sep 03, 2014 at 09:04:37AM +0200, Magnus Therning wrote:
> > For various reasons I'm looking into not using `makechrootpkg` when
> > building the 200+ packages I put into a non-official repo. Obviously
> > it's important to ke
On Wed, Sep 03, 2014 at 12:36:23PM -0400, Leonid Isaev wrote:
> On Wed, Sep 03, 2014 at 09:04:37AM +0200, Magnus Therning wrote:
> > For various reasons I'm looking into not using `makechrootpkg` when
> > building the 200+ packages I put into a non-official repo. Obviously
> > it's important to ke
On Wed, Sep 03, 2014 at 09:04:37AM +0200, Magnus Therning wrote:
> For various reasons I'm looking into not using `makechrootpkg` when
> building the 200+ packages I put into a non-official repo. Obviously
> it's important to keep the building environment separate from my
> ordinary system environ
On Wed, Sep 03, 2014 at 09:17:32AM +0100, Mauro Santos wrote:
> On 03-09-2014 08:04, Magnus Therning wrote:
> > For various reasons I'm looking into not using `makechrootpkg` when
> > building the 200+ packages I put into a non-official repo. Obviously
> > it's important to keep the building envir
On 03-09-2014 08:04, Magnus Therning wrote:
> For various reasons I'm looking into not using `makechrootpkg` when
> building the 200+ packages I put into a non-official repo. Obviously
> it's important to keep the building environment separate from my
> ordinary system environment. Going to full
For various reasons I'm looking into not using `makechrootpkg` when
building the 200+ packages I put into a non-official repo. Obviously
it's important to keep the building environment separate from my
ordinary system environment. Going to full virtualisation is
definitely overkill and the only c
14 matches
Mail list logo