Re: [SCIENTIFIC-LINUX-USERS] Missing zoneinfo files in sl:7 docker image

2019-10-21 Thread Pat Riehecky
I've got a new container build staged up : https://github.com/docker-library/official-images/pull/6824 This will ship the full tzdata zone list.  I will recommend bind mounting the zoneinfo from the host to ensure all files are updated, but this provides a suitable fallback. Pat On

Re: [SCIENTIFIC-LINUX-USERS] Missing zoneinfo files in sl:7 docker image

2019-10-18 Thread Pat Riehecky
I'll take a look. I believe the initial plan was to pull zone info in via something dynamic from the host, but I don't honestly remember... Pat On 10/18/19 5:02 AM, Duncan MacLeod wrote: Hi all, I think there's an issue with the sl:7 docker image (at least the one that&#x

Missing zoneinfo files in sl:7 docker image

2019-10-18 Thread Duncan MacLeod
Hi all, I think there's an issue with the sl:7 docker image (at least the one that's available as of today, Oct 18 2019, digest included below), namely that tzdata is quoted as installed, but the actual contents of that package aren't there. This breaks functionality in python-

Re: [SCIENTIFIC-LINUX-USERS] Problem with recent docker packages?

2019-06-10 Thread Phil Gold
ll look into this. > > > > Pat > > > > On 6/10/19 9:59 AM, Phil Gold wrote: > > > I've been having two problems with the newest docker packages in the > > > sl-extras repository for Scientific Linux 7.  I'm not sure where to > > >

Re: [SCIENTIFIC-LINUX-USERS] Problem with recent docker packages?

2019-06-10 Thread Pat Riehecky
I've dropped a possible fix package in the sl-testing repo. Can you try it to see if this resolves your issue? On 6/10/19 1:05 PM, Pat Riehecky wrote: I'll look into this. Pat On 6/10/19 9:59 AM, Phil Gold wrote: I've been having two problems with the newest docker packages i

Re: [SCIENTIFIC-LINUX-USERS] Problem with recent docker packages?

2019-06-10 Thread Pat Riehecky
I'll look into this. Pat On 6/10/19 9:59 AM, Phil Gold wrote: I've been having two problems with the newest docker packages in the sl-extras repository for Scientific Linux 7. I'm not sure where to report them so hopefully someone here will help. The first problem appea

Problem with recent docker packages?

2019-06-10 Thread Phil Gold
I've been having two problems with the newest docker packages in the sl-extras repository for Scientific Linux 7. I'm not sure where to report them so hopefully someone here will help. The first problem appears to be one of packaging. The systemd unit file for docker-1.13.1-96.gitb

Re: Docker installation

2018-08-09 Thread Steven C Timm
We are using the one from docker-ce-stable on the main grid clusters at Fermilab. All our jobs run inside these containers. Didn't know the sl-extra ones even were out there. Steve Timm From: owner-scientific-linux-us...@listserv.fnal.gov on beha

Docker installation

2018-08-09 Thread Boris Goldowsky
What is the difference between the docker packages in the sl-extras repository and the ones from docker-ce-stable (as recommended by https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.docker.com_install_linux_docker-2Dce_centos_&d=DwIGaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySV

Re: Error message from docker-pr server: any explanations, please?

2018-01-21 Thread Dan
On Wed, 22 Nov 2017, Dan wrote: On my SL7.4 laptop, I have docker-pr listening for https connections. (Within docker, I have a locally-compiled copy of elabftw running an electronic lab book service.) When I point my web browser (Firefox) on the same machine to https://localhost, I initially

Error message from docker-pr server: any explanations, please?

2017-11-22 Thread Dan
Dear All, On my SL7.4 laptop, I have docker-pr listening for https connections. (Within docker, I have a locally-compiled copy of elabftw running an electronic lab book service.) When I point my web browser (Firefox) on the same machine to https://localhost, I initially get a "Your conne

Re: [SCIENTIFIC-LINUX-USERS] docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-29 Thread Mikkel Kruse Johnsen
Hi The problem is related to this line, that is added to /usr/lib/systemd/system/docker.service in the new version. It was not in the old version. Requires=rhel-push-plugin.socket In what package is the file provided ? docker rpm should require that package. -- Med Venlig Hilsen / Kind

Re: [SCIENTIFIC-LINUX-USERS] docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-21 Thread Denice
On Fri, 21 Apr 2017, Pat Riehecky wrote: On 04/21/2017 12:13 PM, Denice wrote: However the corresponding container-selinux package requires policycoreutils >= 2.5-11. That version of policycoreutils is not yet published in the SL updates tree, but should appear soon - it is in fastbugs, so

Re: [SCIENTIFIC-LINUX-USERS] docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-21 Thread Pat Riehecky
On 04/21/2017 12:13 PM, Denice wrote: However the corresponding container-selinux package requires policycoreutils >= 2.5-11. That version of policycoreutils is not yet published in the SL updates tree, but should appear soon - it is in fastbugs, so you would need to enable fastbugs to update it

Re: docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-21 Thread Denice
On Thu, 20 Apr 2017, Mikkel Kruse Johnsen wrote: Hi After an update to "docker-1.12.6-11.el7.x86_64" the service is unable to start. # systemctl start docker.service Failed to start docker.service: Unit not found. disable/enable/stop is working. I see that the ending is "sl7

Re: [SCIENTIFIC-LINUX-USERS] docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-20 Thread Pat Riehecky
I'm not seeing any errors on my boxes. Pat On 04/20/2017 02:12 AM, Mikkel Kruse Johnsen wrote: Hi After an update to "docker-1.12.6-11.el7.x86_64" the service is unable to start. # systemctl start docker.service Failed to start docker.service: Unit not found. disable

docker-1.12.6-11.el7.x86_64 not working with systemd

2017-04-20 Thread Mikkel Kruse Johnsen
Hi After an update to "docker-1.12.6-11.el7.x86_64" the service is unable to start.  # systemctl start docker.service Failed to start docker.service: Unit not found. disable/enable/stop is working. I see that the ending is "sl7" where the old package is "el7".

Re: Docker

2015-02-16 Thread Tom H
On Sun, Feb 15, 2015 at 9:59 AM, wrote: > On Tue, Feb 15, 2015, Tom H wrote: >> >> Of course errors can happen. I'd expect RH to fix them quickly because >> it's in its interest for RHEL rebuilders to publish a distro as >> similar to RHEL as possible. > > How so? Red Hat wants people to buy the

Re: Docker

2015-02-15 Thread Jamie Duncan
e. It truly is that simple. On Sun, Feb 15, 2015 at 9:59 AM, wrote: > Sent from my BlackBerry 10 smartphone. > Original Message > From: Tom H > Sent: Sunday, February 15, 2015 09:08 > To: SL Users > Subject: Re: Docker > > On Tue, Feb 3, 2015 at 10:06 PM, Nico Kadel-Garc

Re: Docker

2015-02-15 Thread prmarino1
Sent from my BlackBerry 10 smartphone.   Original Message   From: Tom H Sent: Sunday, February 15, 2015 09:08 To: SL Users Subject: Re: Docker On Tue, Feb 3, 2015 at 10:06 PM, Nico Kadel-Garcia wrote: > On Tue, Feb 3, 2015 at 12:17 PM, Tom H wrote: >> 1) RH doesn't license RHE

Re: Docker

2015-02-15 Thread Tom H
On Tue, Feb 3, 2015 at 10:06 PM, Nico Kadel-Garcia wrote: > On Tue, Feb 3, 2015 at 12:17 PM, Tom H wrote: >> 1) RH doesn't license RHEL; it provides subscriptions to RHEL. The >> individual have licenses... > > I think you meant "individual components have licenses", It's cool. Indeed, thanks.

Re: Docker

2015-02-15 Thread Tom H
On Tue, Feb 3, 2015 at 8:08 PM, wrote: >> >> 1) RH doesn't license RHEL; it provides subscriptions to RHEL. The >> individual have licenses... >> >> 2) What might be the rationale for RH to release SRPMs (as SRPMs >> previously and as a git tree now) that are different from the SRPMs >> from which

Re: Docker

2015-02-03 Thread Nico Kadel-Garcia
On Tue, Feb 3, 2015 at 12:17 PM, Tom H wrote: > 1) RH doesn't license RHEL; it provides subscriptions to RHEL. The > individual have licenses... I think you meant "individual components have licenses", It's cool. > 2) What might be the rationale for RH to release SRPMs (as SRPMs > previously an

Re: Docker

2015-02-03 Thread prmarino1
ne for a few days. Sent from my BlackBerry 10 smartphone.   Original Message   From: Tom H Sent: Tuesday, February 3, 2015 12:18 To: SL Users Subject: Re: Docker On Mon, Feb 2, 2015 at 6:25 PM, Yasha Karant wrote: > On 02/02/2015 11:35 AM, Connie Sieh wrote: >> On Fri, 30 Jan 2015, Yash

Re: Docker

2015-02-03 Thread Tom H
On Mon, Feb 2, 2015 at 6:25 PM, Yasha Karant wrote: > On 02/02/2015 11:35 AM, Connie Sieh wrote: >> On Fri, 30 Jan 2015, Yasha Karant wrote: >>> >>> Presumably, any application that will run under CentOS, in particular, >>> CentOS 7 that is the RHEL source release for other ports, such as SL 7, >>

Re: Docker

2015-02-03 Thread David Sommerseth
On 03/02/15 17:12, Yasha Karant wrote: > To be clear, the legal language may be "license for fee", "subscription > for fee", or "stand on your head for fee". The operative language is > "FEE". The RHEL 7 binary executable and the RPM updates are not > available from Red Hat (not CentOS, SL, etc.

Re: Docker

2015-02-03 Thread Jamie Duncan
2015 11:35 AM, Connie Sieh wrote: >>> >>>> On Fri, 30 Jan 2015, Yasha Karant wrote: >>>> >>>> On 01/30/2015 10:32 AM, Brett Viren wrote: >>>>> >>>>>> Yasha Karant writes: >>>>>> >>>>>>

Re: Docker

2015-02-03 Thread Yasha Karant
application that does not run under Wine/CrossOver work under Docker under SL 7 the same as it would under VirtualBox with a full install of say MS Win 8.1 (soon MS Win 10)? Docker containers run on Linux (the kernel) so, no, if your application requires honest-to-badness MicroSoft Windows don't pl

Re: Docker

2015-02-03 Thread David Sommerseth
e, will a >>>>> legally licensed MS Win application that does not run under >>>>> Wine/CrossOver work under Docker under SL 7 the same as it would under >>>>> VirtualBox with a full install of say MS Win 8.1 (soon MS Win 10)? >>>> Docker co

Docker on SL, was Re: SL: not a good choice as a workstation

2014-11-09 Thread Nico Kadel-Garcia
SL6 container, until we get enough time to >> > make it work on SL7 natively (after which we'll move it from container >> > to base system)". >> > Having nearly complete virtual host with sshd, postgresql server and >> > related tools would be cumbersome