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

Unable to build AMD64 image with versions locked in #382

Closed
Dashboy1998 opened this issue Feb 13, 2024 · 4 comments · Fixed by #385
Closed

Unable to build AMD64 image with versions locked in #382

Dashboy1998 opened this issue Feb 13, 2024 · 4 comments · Fixed by #385

Comments

@Dashboy1998
Copy link
Contributor

Describe the bug

I am unable to build the image with the current apt-get install package-version as the version seems to be breaking it.

To Reproduce

Steps to reproduce the behavior:

  1. Attempt to build

Expected behavior

Should build

Actual behavior

=> ERROR [palworld stage-3 1/6] RUN apt-get update && apt-get install -y   1.7s
------                                                                           
 > [palworld stage-3 1/6] RUN apt-get update && apt-get install -y --no-install-recommends     procps=2:3.3.17-5     wget=1.21-1+deb11u1     gettext-base=0.21-4     xdg-user-dirs=0.17-2     jo=1.3-2     && apt-get clean     && rm -rf /var/lib/apt/lists/*:
0.223 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
0.262 Get:2 http://deb.debian.org/debian bookworm-updates InRelease [52.1 kB]
0.275 Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
0.301 Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8786 kB]
0.429 Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [12.7 kB]
0.429 Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [137 kB]
0.960 Fetched 9187 kB in 1s (11.6 MB/s)
0.960 Reading package lists...
1.271 Reading package lists...
1.595 Building dependency tree...
1.690 Reading state information...
1.694 Package wget is not available, but is referred to by another package.
1.694 This may mean that the package is missing, has been obsoleted, or
1.694 is only available from another source
1.694 
1.694 Package procps is not available, but is referred to by another package.
1.694 This may mean that the package is missing, has been obsoleted, or
1.694 is only available from another source
1.694 However the following packages replace it:
1.694   libproc2-0
1.694 
1.694 Package gettext-base is not available, but is referred to by another package.
1.694 This may mean that the package is missing, has been obsoleted, or
1.694 is only available from another source
1.694 However the following packages replace it:
1.694   libasprintf0v5
1.694 
1.694 Package xdg-user-dirs is not available, but is referred to by another package.
1.694 This may mean that the package is missing, has been obsoleted, or
1.694 is only available from another source
1.694 
1.694 Package jo is not available, but is referred to by another package.
1.694 This may mean that the package is missing, has been obsoleted, or
1.694 is only available from another source
1.694 
1.696 E: Version '2:3.3.17-5' for 'procps' was not found
1.696 E: Version '1.21-1+deb11u1' for 'wget' was not found
1.696 E: Version '0.21-4' for 'gettext-base' was not found
1.696 E: Version '0.17-2' for 'xdg-user-dirs' was not found
1.696 E: Version '1.3-2' for 'jo' was not found
------
failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends     procps=2:3.3.17-5     wget=1.21-1+deb11u1     gettext-base=0.21-4     xdg-user-dirs=0.17-2     jo=1.3-2     && apt-get clean     && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100

Screenshots

OS information

  • OS:
  • Palworld Version:
  • Docker Image Version:

Hardware information

N/A

docker-compose.yml contents

Default

Container/Host Logs

N/A

Additional context

Removing all the version specifications and it works

@thijsvanloef
Copy link
Owner

This is caused by the AMD base image being updated https://hub.docker.com/r/cm2network/steamcmd/tags

@Dashboy1998
Copy link
Contributor Author

This is caused by the AMD base image being updated https://hub.docker.com/r/cm2network/steamcmd/tags

Looks like they don't have versions so we can't lock it to the specific image tag.

@thijsvanloef
Copy link
Owner

Opened an issue on his Github and he is working on it! CM2Walki/steamcmd#56

@Dashboy1998
Copy link
Contributor Author

Opened an issue on his Github and he is working on it! CM2Walki/steamcmd#56

Awesome. Once they do that we can lock it in to prevent this in the future.

@thijsvanloef thijsvanloef linked a pull request Feb 13, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants