You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on an R package (outsider.base) that makes use of Docker with linux containers.
So far, I've found that it is possible to have Docker running from initiation when using the "Windows Server 2019" image (a so-called "heterogeneous build"). (Note: The image requires a request for access.)
Using this image though seems to lead to an "R command not found" error: Failing example
There is no problem if I drop the "Windows Server 2019" image: Passing example
But then large elements of my code that depend on Docker are not being tested.
Any ideas on how I might solve this issue?
I found a simple issue (26) to do with R not being mounted on E:. Presumably though this issue was corrected and shouldn't be the same cause in this instance. (Although, in my builds I get the message "R is now available on drive C:".)
Hi!
I'm working on an R package (
outsider.base
) that makes use of Docker with linux containers.So far, I've found that it is possible to have Docker running from initiation when using the "Windows Server 2019" image (a so-called "heterogeneous build"). (Note: The image requires a request for access.)
Using this image though seems to lead to an "R command not found" error:
Failing example
There is no problem if I drop the "Windows Server 2019" image:
Passing example
But then large elements of my code that depend on Docker are not being tested.
Any ideas on how I might solve this issue?
I found a simple issue (26) to do with R not being mounted on
E:
. Presumably though this issue was corrected and shouldn't be the same cause in this instance. (Although, in my builds I get the message "R is now available on drive C:".)Useful links
Current Appveyor script
Appveyor project home
The text was updated successfully, but these errors were encountered: