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

Error building the 2.0.69 release #636

Closed
bogatkaj opened this issue Oct 25, 2023 · 3 comments · Fixed by #639
Closed

Error building the 2.0.69 release #636

bogatkaj opened this issue Oct 25, 2023 · 3 comments · Fixed by #639
Assignees
Labels
bug_Normal Normal bug, Server connects to clients but won't sync data
Milestone

Comments

@bogatkaj
Copy link

bogatkaj commented Oct 25, 2023

Hey,
I hope someone may could help.
I'm trying to build the 2.0.69 release with docker build.
The command I use is:

docker build --label org.freetakteam.server -t free-tak-server:2.0.69 .

Build environment is my server running Debian 11 with kernel 5.10.0-23-amd64

The build process gives me the following error:

  Attempting uninstall: Flask
    Found existing installation: Flask 3.0.0
    Uninstalling Flask-3.0.0:
      Successfully uninstalled Flask-3.0.0
  WARNING: The script flask is installed in '/home/freetak/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  Attempting uninstall: Flask-Login
    Found existing installation: Flask-Login 0.6.2
    Uninstalling Flask-Login-0.6.2:
      Successfully uninstalled Flask-Login-0.6.2
  Running setup.py develop for FreeTAKServer
    error: subprocess-exited-with-error

    × python setup.py develop did not run successfully.
    │ exit code: 1
    ╰─> [6 lines of output]
        running develop
        running egg_info
        creating FreeTAKServer.egg-info
        /usr/local/lib/python3.8/site-packages/setuptools/dist.py:697: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
          warnings.warn(
        error: could not create 'FreeTAKServer.egg-info': Permission denied
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× python setup.py develop did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
    running develop
    running egg_info
    creating FreeTAKServer.egg-info
    /usr/local/lib/python3.8/site-packages/setuptools/dist.py:697: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
      warnings.warn(
    error: could not create 'FreeTAKServer.egg-info': Permission denied
    [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

[notice] A new release of pip is available: 23.0.1 -> 23.3.1
[notice] To update, run: pip install --upgrade pip
The command '/bin/sh -c pip3 install -e /FreeTAKServer' returned a non-zero code: 1

I gave 777 permission to all files included in the archive just to get sure, but it didn't solved the issue and I wasn't abled to find another issue with this error, maybe someone has a quick solution.

@RadioAndrea RadioAndrea self-assigned this Nov 18, 2023
@RadioAndrea
Copy link
Collaborator

Hey @bogatkaj,

I also found a lot of issues when building a container when I was reworking our actions infrastructure.

I created this dockerfile in the process. I have designed it specifically for the next release, and not the exact version you are trying to build, but you can give it a shot and see if it results in a good build.

Just mind the volume you'll need to mount somewhere when you run it.

This was linked to pull requests Nov 18, 2023
@RadioAndrea RadioAndrea added the bug_Normal Normal bug, Server connects to clients but won't sync data label Nov 18, 2023
@brothercorvo brothercorvo added this to the 2.2 milestone Nov 28, 2023
@RadioAndrea
Copy link
Collaborator

To future users, it is possible that this is caused due to using python 3.8 instead of python 3.11, and the docker builds have completely changed since this was posted.

Will close this if no response soon.

@bogatkaj
Copy link
Author

Sorry,
I will test it soon as I have more time next week.. currently I'm a bit busy.

Thanks for the support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug_Normal Normal bug, Server connects to clients but won't sync data
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants