similar to: Running CentOS 6 in a Docker container on a non-CentOS host

On Wed, 4 Mar 2020 16:56:02 -0500 Alfred von Campe <alfred at von-campe.com> wrote: > I have to support a legacy build that runs on CentOS 6. I?m new to > Docker and would like to use the official CentOS 6.10 image > (https://github.com/CentOS/sig-cloud-instance-images/blob/da050e2fc6c28d8d72d8bf78c49537247b5ddf76/docker/Dockerfile >

> On Mar 5, 2020, at 6:05, Peter Kjellstr?m wrote: > > You can use singularity. The following example makes an image by > pulling from centos on dockerhub: Interesting! However, I would prefer to use more ?native? Docker commands, as I would rather not have all developers install and configure Singularity when they already have Docker installed on their systems. There has got to be

Hi everybody. Just wanted to mention that I've published a docker image of tinc 1.1pre15 for the raspberry pi 2/3. It was compiled from source on a raspberry 3 and published as byscontrol/tinc-rpi <https://hub.docker.com/r/byscontrol/tinc-rpi/> along witht the configuration instructions. The latest tag refers to 1.1pre15 only, but I can publish other versions as well if needed. Hope

My dockerfile: FROM python:3 WORKDIR /usr/src/app COPY requirements.txt ./ COPY languageserver-master ./ COPY radian-master ./ RUN pip3 install --no-cache-dir -r requirements.txt EXPOSE 8080 RUN apt-key adv --keyserver keys.gnupg.net --recv-key 'E19F5F87128899B192B1A2C2AD5F960A256A04AF' RUN echo "deb http://cloud.r-project.org/bin/linux/debian buster-cran40/" >>

I continue to receive an error installing R via dockerfile on a buster image python:3. E: The value 'buster-cran40' is invalid for APT::Default-Release as such a release is not available in the sources My starting point is the debian buster based Python:3 image adding a couple of python specific configurations and then using the commands in the R project documentation for installing R on

Am 03.09.18 um 15:12 schrieb Robert Marcano via samba: > On 09/03/2018 04:10 AM, Stefan G. Weichinger via samba wrote: >> >> As I am learning docker lately I came to the idea of using a docker >> container as a "fallback" DC at sites where there is no budget (or >> understanding) for a 2nd physical DC. >> >> That 2nd DC *might* run as docker

On Fri, 29 Jan 2016 06:31, Keith Keller <kkeller at ...> wrote: > On 2016-01-29, reynierpm at gmail.com <reynierpm at gmail.com> wrote: >> >> I am building a Dockerfile and I am setting up MariaDB repos as follow: > > This question is probably way offtopic for a CentOS mailing list. > >> # Setup MariaDB repos >> RUN touch

Following my questions in https://lists.samba.org/archive/samba/2019-July/224115.html and the lack of recent builds of Samba in Ubuntu, I started to build Samba on my own. I installed a new virtual machine with Ubuntu 18.04.2 (LTS) server (+ssh), installed docker and docker-compose, and then tried to build using the following Dockerfile: --- Dockerfile begin --- #

Hi, In the samba 4.18.5 source, while installing pre-requisite packages using boothstrap.sh file, in the same folder, I saw the Dockerfile. Can I safely assume that the Samba AD can actually run in Docker? -- Thanks & Regards, Raghav DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to Exzatech Consulting And Services Pvt. Ltd., Bangalore,

I am working in a Dockerfile but there is a "secure" MariaDB server script I need to run which is interactive and I don't know how to deal with this. Basically this is the flow I have follow on the script at test environment and is the same I want to achieve in the Dockerfile without user interaction by just answering as you seen on the flow below: #

Hi all I'm facing an issue while running dovecot inside a singularity (https://sylabs.io/singularity/) container dovecot version is 2.3.4.1 (configuration below) running on debian buster, inside a container made with singularity version 3.4.2 unfortunately, when I try to start dovecot, it gives: Singularity test.sif:~> cat /var/log/mail.log Dec 30 17:23:38 testnode dovecot: master:

Am 03.09.18 um 17:21 schrieb Robert Marcano: > On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: >> great, thanks! Which docker image do you use as base image? > > Sent to you a copy of this email with an attachment of the Dockerfile > needed to build the container image. There are two Dockerfile there, one > for Fedora (extremely experimental Samba package there,

I am building a Dockerfile and I am setting up MariaDB repos as follow: # Setup MariaDB repos RUN touch /etc/yum.repos.d/MariaDB.repo I should write this inside the MariaDB.repo file: [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/5.5/centos6-amd64 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1 What's the right way to do this? The one below? echo

Hi: I have a Dockerfile, which builds an image which installed R 3.3.2 in Ubuntu 14.04, but building using that Dockerfile seems to have stopped working and I am unclear why. I believe the relevant error is: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet

On Monday, August 7, 2023 6:05:03 AM EDT Andrew Bartlett via samba wrote: > https://github.com/samba-in-kubernetes > Andrew, thanks a bunch for pointing people to our org! I really appreciate it. More below... > On Mon, 2023-08-07 at 11:08 +0200, Joachim Lindenberg via samba wrote: > > Hello Anantha, Michael, > > IIRC this is somewhat optimistic or a secret sausage. For

On Mon, 9 Mar 2020 16:16:01 -0400 Alfred von Campe <alfred at von-campe.com> wrote: > > On Mar 5, 2020, at 6:05, Peter Kjellstr?m wrote: > > > > You can use singularity. The following example makes an image by > > pulling from centos on dockerhub: > > Interesting! However, I would prefer to use more ?native? Docker > commands, as I would rather not have

On Sun, Jul 12, 2020 at 11:16:01PM +0300, Nir Soffer wrote: > On Sat, Jul 11, 2020 at 11:18 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > KubeVirt is a custom resource (a kind of plugin) for Kubernetes which > > adds support for running virtual machines. As part of this they have > > the same problems as everyone else of how to import large disk images

>>>>> Jan Gorecki writes: > So the unique.default is from the R tools package during checks. > I don't see those issues on CRAN checks. I cannot reproduce this locally (and have no clues about docker). Perhaps you can try to debug this on your end? And see what env_list is when the error occurs? Best -k > Exact environment where I am reproducing this issue is a

On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: > Am 03.09.18 um 15:12 schrieb Robert Marcano via samba: >> On 09/03/2018 04:10 AM, Stefan G. Weichinger via samba wrote: >>> >>> As I am learning docker lately I came to the idea of using a docker >>> container as a "fallback" DC at sites where there is no budget (or >>>

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its