*From: *Alex Kosolapov
> *Date: *Thursday, December 10, 2020 at 3:44 PM
> *To: *"dev@beam.apache.org"
> *Subject: *Re: Docker Development Environment
>
>
>
> Hi Brian,
>
>
>
> Yes - will update the script, created JIRA to track
> https://issues.apac
Hi!
Wanted to send a note that PR with changes submitted
https://github.com/apache/beam/pull/13545 and ready for code review
Thanks,
Alex
From: Alex Kosolapov
Date: Thursday, December 10, 2020 at 3:44 PM
To: "dev@beam.apache.org"
Subject: Re: Docker Development Environment
Hi B
-To: "dev@beam.apache.org"
Date: Wednesday, December 9, 2020 at 12:21 PM
To: dev
Subject: Re: Docker Development Environment
Hey Alex,
Thanks for trying this out on macOS! Some responses inline
On Tue, Dec 8, 2020 at 11:42 AM Alex Kosolapov
mailto:alex.kosola...@akvelon.com>> wrot
just happened to work when
running from a machine where the HOME dir was the same as in the container.
This one definitely makes sense.
>
>
> If these proposed solutions make sense I will create JIRA ticket and
> submit these improvements for Docker build support on macOS.
>
>
&g
se proposed solutions make sense I will create JIRA ticket and submit
these improvements for Docker build support on macOS.
Thank you,
Alex Kosolapov
From: Brian Hulette
Reply-To: "dev@beam.apache.org"
Date: Friday, December 4, 2020 at 1:15 PM
To: dev
Cc: Omar Ismail
Subject: Re: Docker
I think https://github.com/apache/beam/pull/13308 is about ready to merge.
One question was whether or not to install pyenv in the container - I think
we should try to do without it. Users of this environment will already be
operating within a container, so they shouldn't need pyenv to create
If any of these are suitable for at least some development. I propose we
merge them, and update them with fixes later. Rather than trying to get
things 100% working in the first PR.
Looks like this one was opened in early Sept, and never got merged. Which
is a pretty long time. Perhaps abandoned
I agree this is a good idea. I remember my first experience with Beam
development - I ran through the steps at [1] and had `./gradlew check`
fail. I don't think I ever got it working before moving on and just running
more specific tasks.
It would be great if we had a reliable way for new
Thank you for doing this.
I have seen a few related PRs. Connecting them here in case these efforts
could be combined:
- https://github.com/apache/beam/pull/12837 (/cc +Omar Ismail
)
- https://github.com/apache/beam/pull/13308
Ahmet
On Wed, Nov 25, 2020 at 2:53 PM Sam Rohde wrote:
> Hi All,
