indygreg / indygreg/PyOxidizer

init_fs_encoding on google/cloud-sdk:slim docker image

Open
#624 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

I have managed to get my fairly complicated python application to build even though it contains pandas and numpy. However I noticed that whenever I try and run it on google/cloud-sdk:slim docker image it fails. I traced it down to even hello world application failing without any error other than below
```
error instantiating embedded Python interpreter: during initializing Python main: init_fs_encoding: failed to get the Python codec of the filesystem encoding
```
[Dockerfile.txt](https://github.com/indygreg/PyOxidizer/files/9303044/Dockerfile.txt)
Here is a docker file that builds a helloworld application using python 3.8 on the manylinux build docker and then runs it inside google/cloud-sdk:slim as a minimal repeatable error. I have not tried other python versions yet or other build instances nor using musl as I cannot make standalones with numpy

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked Dockerfile.txt and reproduce the Python 3.8 hello-world build using the manylinux environment, then run it in google/cloud-sdk:slim. Confirm the init_fs_encoding failure and compare the standalone application's runtime assumptions with the container. Done means the failure is explained and the reported standalone application runs successfully in the target image.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, google-cloud, python
Domain
build-system, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.