1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
1
Try to remove the extra =
sign in your requirement.txt: flask==3.0.0
and try again.
I am still receiving the exact same error:
[8/Apr/2024:11:26:38] [deployment:2] Creating your deployment [8/Apr/2024:11:26:54] exec /usr/local/bin/python: exec format error [8/Apr/2024:11:28:03] [deployment:2] Started 1 new node [8/Apr/2024:11:28:12] exec /usr/local/bin/python: exec format error [8/Apr/2024:11:29:03] [deployment:2] Started 1 new node [8/Apr/2024:11:29:09] exec /usr/local/bin/python: exec format error [8/Apr/2024:11:30:16] [deployment:2] Started 1 new node [8/Apr/2024:11:30:21] exec /usr/local/bin/python: exec format error [8/Apr/2024:11:30:33] [deployment:2] Canceled
In this rerun, I repushed the image, and changed my containers.json to
.6
accordingly:{ "flask": { "image": ":flask-service.flask-container.6", "ports": { "5000": "HTTP" } } }
This error is commonly associated with trying to run a binary compiled for a different architecture, such as running an ARM binary on an x86 system or vice versa. Since you are using a standard Python image from Docker Hub (
python:3.12-alpine
), it should be compatible with most x86_64 Linux systems. If your Lightsail instance is using a different architecture, that could be the source of the problem.Try to verify that the Docker image architecture matches the Lightsail instance architecture.
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 8 meses
Are you creating the files on a Windows computer? If your text editor is incorrectly configured, you might be inserting
\r\n
or saving in a file format other than UTF-8.