[Codespaces] docker run in codespaces hits an error
#17296
Labels
EngSys
This issue is impacting the engineering system.
Comments
ghost
added
the
needs-triage
HarshaNalluru
changed the title
docker run in codespacesdocker run in codespaces hits an error
ghost
removed
the
needs-triage
|
This comment sheds some light. I may be able to get the volume working @HarshaNalluru . It'll be the same volume on the host machine, but that's ok. I'll be experimenting with this today. |
|
#17306 fixed the permission issue |
|
Tested again and it works, closing this,. |
openapi-sdkautomation bot
pushed a commit
to AzureSDKAutomation/azure-sdk-for-js
that referenced
this issue
Feb 9, 2022
[NetAppFiles] Anf 17315 net app files 2021 10 01 (Azure#17296) * Add folder for api-version 2021-10-01 * Apply 2021-10-01 Changes * Remove snapshotSingleFile restore example * Revert vs code change to settings * Add unixPermissions to volumePatchProperties * Remove volume Relocation from 2021-10-01 * Remove zones from this api-version * Add Snapshot restoreFiles * Fix newly added validation issue MISSING_PATH_PARAMETER_DEFINITION * Remodel list Replications * Remove listReplication for api-version 2021-10-01 * Fix quotaLimits in examples * Add subvolumes api * Add subvolumes to custom words * Add parentpath custom word * Revert operationId to Volumes_ReplicationStatus * subvolumeProperties size write-only * Revert "subvolumeProperties size write-only" This reverts commit 243bb48ba6e5bea1f742492cfc6496d572103613. * subvolumeProperties size write-only take2 * prettier
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@scbedd found an issue while investigating #17138
Dockerfile update from
...universal:0-linuxto...universal:1-linuxseems to have brokendocker runcommand as shown below.sudo dockerdorsystemctl start dockerwould not work because we don't have root permissions.While we do want to be on the latest image, we would have to fix the issue and avoid reverting to
...universal:0-linux.The older codespaces that are created would work fine, just the new ones would hit the issue.
//cc @jeremymeng
The text was updated successfully, but these errors were encountered: