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
This seems to be because the DockerFile is trying to copy the Common project assuming it's a child of the services/ folder.
When running from Unity, we need to set the DockerBuildContextPath to the unity project root, and set the relative Dockerfile path be relative to the unity root.
The beamservice signpost file has the assetProjectPath field, which needs to map to the Unity project relative path of the service csproj file. Then, that path becomes the main source for the relative dockerfile path, and the build context path is always ., because Unity CLI .beamable contexts are always at the unity root.
The text was updated successfully, but these errors were encountered:
The docker build context is becoming "sort of" implicit. By default, it will become the root of the .beamable folder, however, it needs to be configurable via the configuration-defaults.json file.
The command
beam services run
is not working for standalone microservices that doesn't have the following folder structure:TestService/
----services/
----TestService/
----TestServiceCommon/
----TestService.sln
This seems to be because the DockerFile is trying to copy the Common project assuming it's a child of the
services/
folder.When running from Unity, we need to set the DockerBuildContextPath to the unity project root, and set the relative Dockerfile path be relative to the unity root.
The beamservice signpost file has the
assetProjectPath
field, which needs to map to the Unity project relative path of the service csproj file. Then, that path becomes the main source for the relative dockerfile path, and the build context path is always.
, because Unity CLI .beamable contexts are always at the unity root.The text was updated successfully, but these errors were encountered: