On 10/25/2016 04:30 PM, Josh Berkus wrote:
> On 10/25/2016 12:14 PM, Josh Berkus wrote:
>> On 10/25/2016 12:02 PM, Jeremy Eder wrote:
>>> When you "docker pull golang", the image is over 600MB (and it's built
>>> on alpine).
>>> Same with docker pull java...also > 600MB.
>>>
>>> docker pull alpin
Today, systemd is included with our 7.2 and newer base images. We are
putting the finishing touches on the work Colin started earlier this year
and plan to release a new, minimal base image. I've been toying with the
name rhel7-core, but that name sucks and will likely change. Since the new
minimal
*What* do you intend to surface to users? IIUC, this discussion is specific
to device mapper storage drivers right?
On Tue, Oct 25, 2016 at 5:03 AM, Jeremy Eder wrote:
> Hi,
>
> Vivek Goyal (cc) and I were discussing ways to deliver page cache sharing,
> POSIX compliance and SELinux support with
There has been a lot of talk of also doing this with VFS back end also
(Which is basically standard storage). One of our long term goals with OCID
is to support readonly containers on an NFS store. Which would also
give us the same benefits over a COW file system.
On 10/26/2016 02:20 PM, Vish
If a user specifies read-only in their podspec...what does that translate
to (it might be a distro-specific question). IMO the --shared-rootfs
should be the default when --read-only is specified, but it's not atm.
Vivek has implemented it for devicemapper first. But the intent is that it
will b
IMO, this doesn't really need any new knobs in the pod spec. This could be
handled under the hood in the container runtime level (by config or
default).
On Wed, Oct 26, 2016 at 11:44 AM, Jeremy Eder wrote:
> If a user specifies read-only in their podspec...what does that translate
> to (it mig
Yeah it sounds like it - that's a good place to start, and then if we
realize we need the knob we can come back and decide on an API object
change if necessary.
On Wed, Oct 26, 2016 at 2:46 PM, Mrunal Patel wrote:
> IMO, this doesn't really need any new knobs in the pod spec. This could be
> han
The advantage of setting up a layered image called RHEL7-systemd on top
of RHEL7 is that we could default the two things necessary to run a
systemd container. STOPCMD and CMD. Also we could continue to work to
get systemd out of the RHEL7 base container.
On 10/26/2016 02:36 PM, Ben Breard wrote:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ed0314ad7
We need karma on this package so we can get new docker-storage-setup to take
care of https://bugzilla.redhat.com/show_bug.cgi?id=1387934.
Dusty
I have a serious question about a way to map UIDs inside the container to
UIDs outside it. And a way to specify UID for mounted volumes like /data/
and /app/code/
Let's look to the topic from developer point of view.
I have vagrant sshfs mouting my home into the box.
My home have volumes owned b
10 matches
Mail list logo
