-
Notifications
You must be signed in to change notification settings - Fork 49
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
Docker build not supported on windows: module 'os' has no attribute 'geteuid' #100
Comments
oof, this was my code change. |
without that line the build fails on AL2/AL2012 instances. |
from here hmmm. I'll need to think of a way around this. I wonder how the SAM CLI does this. |
interesting but looks like a known issue - apache/mxnet#13759 |
I had a look at sam-cli and found out, that they don't use "user=..." at all: |
if we remove the user setting, the files created end up being owned by 'root' and the current user can't make any changes to them. this doesn't seem to affect SAM because once the files are made, they're sent to S3 and the current user doesn't need to make any changes to them. I think that because SAM nests the files within a directory that the current user owns, the current user can delete the directory without a problem, but CFN CLI doesn't do the same nesting behavior. |
Ok. What's your preferred solution on that? As right now, it's locking out PC developers because of it. (Of course: Using a VM is possible, but not straightforward :-) ) |
Is there any update on this? This issue is making it impossible for me to author hooks on Windows. This happens even with the demo hook from AWS blog:
The only way to make the hook work is to submit from a Linux machine. |
Yeah disappointing to come back two years later and get bit by the exact same thing :( |
Any updates on the investigation? I really want to test this out and submit my own cfn hooks! With native Windows support, that would make it a lot more convenient for me and others :) |
With #208 builds on Windows machines and any OS where os.geteuid() should get resolved. Part of the fix was a pip upgrade command, which was needed to get builds running using the Python 3.6 container image. This update was breaking the build process on non-Windows machines. This upgrade is not needed is you are using Python 3.7 or higher on Windows. We will be deprecating Python 3.6 soon and we recommend upgrading. If truly required, please
|
The released packages related to this issue |
I didn't see not supporting Windows called out anywhere in the readme
Repro steps
install:
init:
Problem line:
cloudformation-cli-python-plugin/python/rpdk/python/codegen.py
Line 256 in 20f4657
The text was updated successfully, but these errors were encountered: