Hi Divyansh,

You mentioned previously that you were trying to get an R dev setup in
Docker, but that gist looks quite different to what's recommended in the R
dev setup instructions linked above.  It looks like you're trying to set up
a Docker image based on one of our CI jobs which builds the docs for
multiple Arrow implementations, which I wouldn't recommend, as it involves
a lot more steps than you need for an R dev setup, and probably won't be
that useful for the specific task of getting a working R dev setup on
Docker.

I'd recommend instead looking at the article mentioned by me, Bryce, and
Jon [1].  Happy to answer any questions if any issues come up with those
instructions, as they could potentially be made more clear, and it's always
useful to get feedback on docs like these.

Nic

[1] https://arrow.apache.org/docs/r/articles/developers/docker.html

On Fri, 20 Oct 2023 at 08:13, Divyansh Khatri <divyanshkhatri...@gmail.com>
wrote:

> please see this and help me resolve the issue
> https://gist.github.com/Divyansh200102/3ba4f5e391d8e62307f8b584a5a659d8
>
> On Wed, 18 Oct 2023 at 19:14, Jonathan Keane <jke...@gmail.com> wrote:
>
> > For development of the R package with docker containers, the link [1]
> that
> > Nic sent in this same thread is the place to go. In addition to that
> > docker-focused one, there are a handful of others that might prove useful
> > to you in getting your development environment setup [2].
> >
> > If you run into any issues, feel free to post here, but it's helpful to
> do
> > so with debugging mode on (i.e. set the env var ARROW_DEV to true) and to
> > provide the exact commands you sent along with the output you're seeing
> so
> > we can help diagnose what's going wrong.
> >
> > [1] – https://arrow.apache.org/docs/r/articles/developers/docker.html
> > [2] –
> https://arrow.apache.org/docs/r/articles/index.html#developer-guides
> >
> > -Jon
> >
> >
> > On Wed, Oct 18, 2023 at 2:48 AM Divyansh Khatri <
> > divyanshkhatri...@gmail.com>
> > wrote:
> >
> > > I am trying to contribute to the arrow project.so i am trying to setup
> > the
> > > project on locally.
> > >
> > > On Tue, 17 Oct 2023 at 05:14, Bryce Mecum <bryceme...@gmail.com>
> wrote:
> > >
> > > > That error makes it look like you're running `docker compose up` from
> > > > the root of the Arrow source tree which is likely not what you want.
> > > > Are you trying to use the Arrow R package in a Docker container or
> are
> > > > you trying to contribute to it by developing inside of a Docker
> > > > container? Nic's link [1] is a good starting point.
> > > >
> > > > [1] https://arrow.apache.org/docs/r/articles/developers/docker.html
> > > >
> > > > On Mon, Oct 16, 2023 at 4:31 AM Divyansh Khatri
> > > > <divyanshkhatri...@gmail.com> wrote:
> > > > >
> > > > > Hi,so i am basically using the docker cmd 'docker compose up -d' in
> > the
> > > > > docker-compose.yml but i am encountering this error(Error response
> > from
> > > > > daemon: manifest for amd64/maven:3.5.4-eclipse-temurin-8 not found:
> > > > > manifest unknown: manifest unknown)so i am not sure how to proceed
> > from
> > > > > here?
> > > > >
> > > > > On Mon, 16 Oct 2023 at 14:17, Nic Crane <thisis...@gmail.com>
> wrote:
> > > > >
> > > > > > Hi Divyansh,
> > > > > >
> > > > > > There are instructions for creating a R package dev setup here:
> > > > > > https://arrow.apache.org/docs/r/articles/developers/setup.html
> > > > > >
> > > > > > If you can explain a bit more about what you've tried so far and
> > > > what's not
> > > > > > working, we may be able to advise.
> > > > > >
> > > > > > Best wishes,
> > > > > >
> > > > > > Nic
> > > > > >
> > > > > > On Mon, 16 Oct 2023 at 06:02, Divyansh Khatri <
> > > > divyanshkhatri...@gmail.com
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I am having problems regarding setting up the r package using
> > > docker
> > > > of
> > > > > > the
> > > > > > > apache arrow.Can you give me the step by step process of how
> do i
> > > > setup
> > > > > > the
> > > > > > > r package in my vs code system using docker.
> > > > > > >
> > > > > >
> > > >
> > >
> >
>

Reply via email to