Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support dynamic lookup of instance types -> disk mount locations #78

Open
prisamuel opened this issue Apr 23, 2020 · 0 comments
Open

Support dynamic lookup of instance types -> disk mount locations #78

prisamuel opened this issue Apr 23, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@prisamuel
Copy link
Contributor

Changing hub_instance_type = "t3.medium" to a t2 type device gives this error on startup

2020-04-23 11:43:41.220951 I | Mounting volume
2020-04-23 11:43:41.220992 I | Running command mount "$HUB_DEVICE" /opt/dotscience-aws || (set -euo pipefail && mkfs -t ext4 "$HUB_DEVICE" && mount "$HUB_DEVICE" /opt/dotscience-aws) with env [HUB_DEVICE=/dev/nvme1n1]
mount: /opt/dotscience-aws: special device /dev/nvme1n1 does not exist.
mke2fs 1.44.1 (24-Mar-2018)
The file /dev/nvme1n1 does not exist and no size was specified.
2020-04-23 11:43:41.238777 I | Command mount "$HUB_DEVICE" /opt/dotscience-aws || (set -euo pipefail && mkfs -t ext4 "$HUB_DEVICE" && mount "$HUB_DEVICE" /opt/dotscience-aws) failed with exit status 1
panic: exit status 1
@prisamuel prisamuel added the bug Something isn't working label Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant